-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parallel/test-runner-output is flaky #49853
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
test_runner
Issues and PRs related to the test runner subsystem.
Comments
joyeecheung
added
the
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
label
Sep 25, 2023
cc @nodejs/test_runner I think we should mark this and test-runner-watch-mode (#49605) as flaky for now since they've been flaking the CI for months |
joyeecheung
added
the
test_runner
Issues and PRs related to the test runner subsystem.
label
Sep 25, 2023
The report listed in the OP contains a PR related to test runner. Here is another report from 3 days ago without PRs related to test runner: nodejs/reliability#673 (still many different platforms, so I'll just mark it as "flaky on all platforms") |
nodejs-github-bot
pushed a commit
that referenced
this issue
Sep 25, 2023
This has been flaky on many platforms for months. Mark it as flaky for now to avoid blocking the CI. PR-URL: #49854 Refs: #49853 Refs: nodejs/reliability#673 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
+ ' callback called twice in future tick (-*ms)\n' +
- ' callback called twice in future tick (*ms)\n' + + '\t<testsuite name="level 0a" time="-3.984146" disabled="0" errors="0" tests="4" failures="0" skipped="0" hostname="HOSTNAME">\n' +
+ '\t\t<testcase name="level 1a" time="-4.190686" classname="test"/>\n' +
- '\t<testsuite name="level 0a" time="*" disabled="0" errors="0" tests="4" failures="0" skipped="0" hostname="HOSTNAME">\n' +
- '\t\t<testcase name="level 1a" time="*" classname="test"/>\n' +
+ " code: 'ERR_TEST_FAILURE',\n" +
+ " failureType: 'testCodeFailure',\n" +
+ ' cause: Error: thrown from sync fail todo with message\n' +
- " failureType: 'testCodeFailure',\n" +
- ' cause: Error: thrown from sync fail todo with message\n' +
- ' *\n' +
' *\n' +
' *\n' +
' *\n' +
' *\n' +
' *\n' +
+ ' *\n' +
+ ' *\n' +
- ' at async Test.processPendingSubtests (node:internal/test_runner/test:374:7),\n' +
- " code: 'ERR_TEST_FAILURE'\n" +
|
ruyadorno
pushed a commit
that referenced
this issue
Sep 28, 2023
This has been flaky on many platforms for months. Mark it as flaky for now to avoid blocking the CI. PR-URL: #49854 Refs: #49853 Refs: nodejs/reliability#673 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
ruyadorno
pushed a commit
that referenced
this issue
Sep 28, 2023
This has been flaky on many platforms for months. Mark it as flaky for now to avoid blocking the CI. PR-URL: #49854 Refs: #49853 Refs: nodejs/reliability#673 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
alexfernandez
pushed a commit
to alexfernandez/node
that referenced
this issue
Nov 1, 2023
This has been flaky on many platforms for months. Mark it as flaky for now to avoid blocking the CI. PR-URL: nodejs#49854 Refs: nodejs#49853 Refs: nodejs/reliability#673 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
alexfernandez
pushed a commit
to alexfernandez/node
that referenced
this issue
Nov 1, 2023
PR-URL: nodejs#49878 Fixes: nodejs#49853 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
debadree25
pushed a commit
to debadree25/node
that referenced
this issue
Apr 15, 2024
PR-URL: nodejs#49878 Fixes: nodejs#49853 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
sercher
added a commit
to sercher/graaljs
that referenced
this issue
Apr 25, 2024
PR-URL: nodejs/node#49878 Fixes: nodejs/node#49853 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
sercher
added a commit
to sercher/graaljs
that referenced
this issue
Apr 25, 2024
PR-URL: nodejs/node#49878 Fixes: nodejs/node#49853 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
test_runner
Issues and PRs related to the test runner subsystem.
Test
parallel/test-runner-output
Platform
everywhere
Console output
see output
Build links
parallel/test-runner-output
Additional information
This actually has been flaky for quite some time and fails on many different platforms. The latest report comes from nodejs/reliability#675. It looks like at least in the case shown here the duration should've
duration_ms: *
instead ofduration_ms: ZERO
. But there can be other kind of differences on other platforms.The text was updated successfully, but these errors were encountered: