You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are technically 2 issues (but this report will focus on the memory issue)
Memory increases with every test that is performed.
There was a regression between v23 and v24 which resulted in slower tests
To Reproduce
Steps to reproduce the behavior:
Create a loop of many tests and run them. I tested using 1000 tests in 100 files (100k tests), but the same can be done in a single file. Most obvious when using the --runInBand flag along with --logHeapUsage
Expected behavior
Memory usage should at the very least drop after each file instead of continuing to grow.
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
🐛 Bug Report
There are technically 2 issues (but this report will focus on the memory issue)
To Reproduce
Steps to reproduce the behavior:
Create a loop of many tests and run them. I tested using 1000 tests in 100 files (100k tests), but the same can be done in a single file. Most obvious when using the
--runInBand
flag along with--logHeapUsage
Expected behavior
Memory usage should at the very least drop after each file instead of continuing to grow.
Link to repl or repo (highly encouraged)
v25
Repository
Tests
v24
Repository
Tests
v23
Repository
Tests
To test the above, clone the repo and run
yarn test:debug
envinfo
Despite the above OS/CPU specs, the same can be seen from the linked test results from GitHub Actions.
The text was updated successfully, but these errors were encountered: