testdouble experiencing memory issue when running 800 unit tests
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- javascript, nodejs
- 领域
- testing
调研方向
Start by reproducing the memory growth with the reported 800-test Jenkins scenario using testdouble 3.20.2, then inspect the regression/src directory for a focused failing test. Run npm it after adding a minimal reproduction; done means the retained testdouble usage is reproducible and the cleanup behavior is covered by a regression test.
由索引模型根据 Issue 内容生成。
描述
Description
Running 800 unit tests using testdouble, resulting in memory leak.
Issue
There are many testdouble usages that do not seem to be deleting properly. Therefore, when building on Jenkins, it terminates with the error message:
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
This image comes from a Heap Snapshot of some of the tests.
Our currently code consists of the following, but it doesn't seem to help resolve the memory leak.
afterEach(function () {
td.reset();
});
Are there any other lines that should be included to help with garbage collection?
Environment
-
node -voutput: 18.20.4 -
npm -v(oryarn --version) output: 10.7.0 -
npm ls testdouble(oryarn list testdouble) version: 3.20.2
Failing Test
- Fork the repo
- Add a failing test (probably to the `/regression/src' directory)
- Submit a pull request for the failing test or link to your branch here
Example Repo
- Create a minimal repository that reproduces the issue
- Make sure that a fresh clone can run only
npm itand observe the issue - Link to that repo here
Runkit Notebook
- Create a Runkit notebook
- Invoke
var td = require('testdouble')at the top - Verify the behavior your issue is concerned with by clicking "Run"
- Link to the Runkit here
Code-fenced Examples
var td = require('testdouble')
// Your steps here.
- 主要语言
- JavaScript
- 星标
- 1.4k
- 派生
- 140
- 平均合并
- 5 小时 55 分钟
- 30 天内合并 PR
- 4
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
testdouble/testdouble.js 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 45/100
testdouble/testdouble.js#538 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 45/100
testdouble/testdouble.js#537 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
testdouble/testdouble.js#536 ·
-
难度 1/5 1 小时以内 新手友好度 45/100
testdouble/testdouble.js#533 ·
-
难度 4/5 3-5 天 新手友好度 32/100
testdouble/testdouble.js#532 · 1 条评论 ·
查看 testdouble/testdouble.js 的全部 Issue
相似的 Issue
-
automation models
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
needs:triage
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
enhancement status: needs triage
难度 2/5 1-3 小时 新手友好度 88/100
mastra-ai/mastra#25508 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
agentic-workflows
难度 1/5 1 小时以内 新手友好度 72/100
githubnext/gh-aw-cao#15017 ·
维护者通常 1 天内回复