-
Notifications
You must be signed in to change notification settings - Fork 11
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
CI Reliability 2023-05-25 #576
Comments
kvakil
added a commit
to kvakil/node
that referenced
this issue
May 25, 2023
This test has been failing occasionally since it was introduced ~5 days ago. It was the nodejs#1 failing JS test in the most recent reliability report. Mark it as flaky. Fixes: nodejs#48180 Refs: nodejs#47986 Refs: nodejs/reliability#576
kvakil
added a commit
to kvakil/node
that referenced
this issue
May 25, 2023
This test has been failing occasionally since it was introduced ~5 days ago. It was the most common failing JS test in the most recent reliability report. Mark it as flaky. Fixes: nodejs#48180 Refs: nodejs#47986 Refs: nodejs/reliability#576
nodejs-github-bot
pushed a commit
to nodejs/node
that referenced
this issue
May 27, 2023
This test has been failing occasionally since it was introduced ~5 days ago. It was the most common failing JS test in the most recent reliability report. Mark it as flaky. Fixes: #48180 Refs: #47986 Refs: nodejs/reliability#576 PR-URL: #48181 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
May 30, 2023
This test has been failing occasionally since it was introduced ~5 days ago. It was the most common failing JS test in the most recent reliability report. Mark it as flaky. Fixes: #48180 Refs: #47986 Refs: nodejs/reliability#576 PR-URL: #48181 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
danielleadams
pushed a commit
to nodejs/node
that referenced
this issue
Jul 6, 2023
This test has been failing occasionally since it was introduced ~5 days ago. It was the most common failing JS test in the most recent reliability report. Mark it as flaky. Fixes: #48180 Refs: #47986 Refs: nodejs/reliability#576 PR-URL: #48181 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
MoLow
pushed a commit
to MoLow/node
that referenced
this issue
Jul 6, 2023
This test has been failing occasionally since it was introduced ~5 days ago. It was the most common failing JS test in the most recent reliability report. Mark it as flaky. Fixes: nodejs#48180 Refs: nodejs#47986 Refs: nodejs/reliability#576 PR-URL: nodejs#48181 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
Ceres6
pushed a commit
to Ceres6/node
that referenced
this issue
Aug 14, 2023
This test has been failing occasionally since it was introduced ~5 days ago. It was the most common failing JS test in the most recent reliability report. Mark it as flaky. Fixes: nodejs#48180 Refs: nodejs#47986 Refs: nodejs/reliability#576 PR-URL: nodejs#48181 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
Ceres6
pushed a commit
to Ceres6/node
that referenced
this issue
Aug 14, 2023
This test has been failing occasionally since it was introduced ~5 days ago. It was the most common failing JS test in the most recent reliability report. Mark it as flaky. Fixes: nodejs#48180 Refs: nodejs#47986 Refs: nodejs/reliability#576 PR-URL: nodejs#48181 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Failures in node-test-pull-request/51863 to node-test-pull-request/51956 that failed more than 2 PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)CCTest Failure
../test/cctest/test_inspector_socket.cc:323: Failure
Example
Jenkins Failure
Build timed out (after 60 minutes). Marking the build as failed.
Example
Build Failure
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Example
error: The last gc run reported the following. Please correct the root cause
Example
error: ld returned 1 exit status
Example
fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)
Example
JSTest Failure
js-native-api/test_cannot_run_js/test
Example
parallel/test-http-remove-connection-header-persists-connection
Example
parallel/test-runner-output
Example
parallel/test-runner-watch-mode
Example
pummel/test-net-throttle
Example
sequential/test-worker-prof
Example
parallel/test-http-request-join-authorization-headers
Example
wpt/test-timers
Example
wpt/test-webcrypto
Example
parallel/test-fs-watch-recursive-add-file
Example
parallel/test-fs-watch-recursive-add-file-with-url
Example
parallel/test-fs-watch-recursive-symlink
Example
parallel/test-inspector-debug-end
Example
parallel/test-single-executable-application
Example
parallel/test-tls-ticket-cluster
Example
Progress
../test/cctest/test_inspector_socket.cc:323: Failure
(3)Build timed out (after 60 minutes). Marking the build as failed.
(2)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
(9)error: The last gc run reported the following. Please correct the root cause
(2)error: ld returned 1 exit status
(2)fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)
(2)js-native-api/test_cannot_run_js/test
(10)parallel/test-http-remove-connection-header-persists-connection
(8)parallel/test-runner-output
(5)parallel/test-runner-watch-mode
(4)pummel/test-net-throttle
(4)sequential/test-worker-prof
(4)parallel/test-http-request-join-authorization-headers
(3)wpt/test-timers
(3)wpt/test-webcrypto
(3)parallel/test-fs-watch-recursive-add-file
(2)parallel/test-fs-watch-recursive-add-file-with-url
(2)parallel/test-fs-watch-recursive-symlink
(2)parallel/test-inspector-debug-end
(2)parallel/test-single-executable-application
(2)parallel/test-tls-ticket-cluster
(2)The text was updated successfully, but these errors were encountered: