test_runner: improve --test-timeout to be per test#57672
test_runner: improve --test-timeout to be per test#57672nodejs-github-bot merged 10 commits intonodejs:mainfrom
Conversation
|
Review requested:
|
fba5496 to
a982c95
Compare
b79d0c3 to
496c282
Compare
Previously `--test-timeout` is set on per test execution, this is obviously a bug as per test execution is hard to be expected, this patch addresses the issue by setting `timeout` from per execution to per test. This patch also fixes a minor issue that `--test-timeout` is not being respected when running without `--test`.
496c282 to
c1c48ec
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #57672 +/- ##
========================================
Coverage 90.22% 90.23%
========================================
Files 630 630
Lines 185055 185296 +241
Branches 36216 36342 +126
========================================
+ Hits 166975 167204 +229
+ Misses 11042 11011 -31
- Partials 7038 7081 +43
🚀 New features to boost your workflow:
|
cjihrig
left a comment
There was a problem hiding this comment.
A few nits, but this is looking a lot better than the current implementation. Thanks!
250ef6d to
8a713ec
Compare
8a713ec to
af2201e
Compare
1f2245c to
f593a7b
Compare
…Suite, unref timeout
f593a7b to
6559293
Compare
cjihrig
left a comment
There was a problem hiding this comment.
LGTM. Thanks for getting this done!
|
Hey @jakecastelli, it seems there's a failure in the CI: https://ci.nodejs.org/job/node-test-binary-windows-js-suites/33540/ ...It's the first time I've seen that specific test be "flaky" |
|
hmm not too sure, I will keep an eye on the reliability report going forward for that test |
|
Landed in 67786c1 |
|
Thank you! |
Previously `--test-timeout` is set on per test execution, this is obviously a bug as per test execution is hard to be expected, this patch addresses the issue by setting `timeout` from per execution to per test. This patch also fixes a minor issue that `--test-timeout` is not being respected when running without `--test`. PR-URL: nodejs#57672 Fixes: nodejs#57656 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Pietro Marchini <pietro.marchini94@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Previously `--test-timeout` is set on per test execution, this is obviously a bug as per test execution is hard to be expected, this patch addresses the issue by setting `timeout` from per execution to per test. This patch also fixes a minor issue that `--test-timeout` is not being respected when running without `--test`. PR-URL: #57672 Fixes: #57656 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Pietro Marchini <pietro.marchini94@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Previously `--test-timeout` is set on per test execution, this is obviously a bug as per test execution is hard to be expected, this patch addresses the issue by setting `timeout` from per execution to per test. This patch also fixes a minor issue that `--test-timeout` is not being respected when running without `--test`. PR-URL: #57672 Fixes: #57656 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Pietro Marchini <pietro.marchini94@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
|
This seemed to cause test failures when cherry-picked to v22.x-staging. It's possible that the tests are relying on test runner features that cannot or have yet to be backported to v22.x-staging. |
Previously
--test-timeoutis set on per test execution, this is obviously a bug as per test execution is hard to be expected, this patch addresses the issue by settingtimeoutfrom per execution to per test.This patch also fixes a minor issue that
--test-timeoutis not being respected when running without--test.Fixes: #57656