Repository navigation
Tests take a long time to run #47146
Description
Activity
- addedtestIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
on Mar 18, 2023 test/parallel/test-single-executable-application.jshas been added recently and it's a slow test. On my Intel Mac, it runs for ~38 seconds but I would expect it to be a bit faster on M2 Pro.The test runner unfortunately doesn't have an option to print the running time of individual tests but lowering the timeout (default is 120 seconds) will identify the slow ones:
$ python tools/test.py -J --timeout 5 paralleltest-webcrypto takes over a minute to run on my system.
$ python tools/test.py -J --timeout 5 === release test-http-server-headers-timeout-keepalive === Path: parallel/test-http-server-headers-timeout-keepalive Command: out/Release/node /Users/mzasso/git/nodejs/node/test/parallel/test-http-server-headers-timeout-keepalive.js --- TIMEOUT --- === release test-http-server-request-timeout-keepalive === Path: parallel/test-http-server-request-timeout-keepalive Command: out/Release/node /Users/mzasso/git/nodejs/node/test/parallel/test-http-server-request-timeout-keepalive.js --- TIMEOUT --- === release test-single-executable-application === Path: parallel/test-single-executable-application Command: out/Release/node /Users/mzasso/git/nodejs/node/test/parallel/test-single-executable-application.js --- TIMEOUT --- [04:11|% 100|+ 3721|- 3]: Done$ time ./node test/parallel/test-http-server-headers-timeout-keepalive.js ./node test/parallel/test-http-server-headers-timeout-keepalive.js 0.11s user 0.02s system 0% cpu 15.088 total $ time ./node test/parallel/test-http-server-request-timeout-keepalive.js ./node test/parallel/test-http-server-request-timeout-keepalive.js 0.11s user 0.02s system 0% cpu 15.090 total $ time ./node test/parallel/test-single-executable-application.js ./node test/parallel/test-single-executable-application.js 18.78s user 0.53s system 98% cpu 19.641 total$ make -s jstest ... [05:27|% 100|+ 3878|- 0]: Done All tests passed.Full run took 5m30s this time. Quite far from the 8 minutes I got last time 🤔
I think #44342 should help this a bit (which should enable us to move these sequential tests to parallel, but I haven't checked locally yet)
- added a commit that references this issue
on Mar 31, 2023 - added 4 commits that reference this issue
on Apr 5, 2023 28 remaining items
- added 5 commits that reference this issue
on Jul 6, 2023 - added 7 commits that reference this issue
on Jul 6, 2023 github-actions commented
on Jun 15, 2026 on Jun 15, 2026 – with GitHub ActionsContributorMore actionsThis issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Jun 15, 2026
There was a time (not so long a go, maybe ~1 year) when
make -s jstesttook 2-3 minutes on my previous computer.Now I have a decent Mac with M2 Pro and the same command takes 8 minutes! I don't know what changed, but I doubt we more than doubled the number of tests since then.
Are there some relatively new tests which are specifically slow?