-
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-26 #577
Comments
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/51868 to node-test-pull-request/51966 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 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
fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)
Example
fatal: No rebase in progress?
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
pummel/test-net-throttle
Example
sequential/test-worker-prof
Example
parallel/test-runner-watch-mode
Example
wpt/test-timers
Example
parallel/test-http-request-join-authorization-headers
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
sequential/test-perf-hooks
Example
Progress
../test/cctest/test_inspector_socket.cc:323: Failure
(4)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
(8)error: The last gc run reported the following. Please correct the root cause
(2)fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)
(2)fatal: No rebase in progress?
(2)js-native-api/test_cannot_run_js/test
(12)parallel/test-http-remove-connection-header-persists-connection
(9)parallel/test-runner-output
(5)pummel/test-net-throttle
(5)sequential/test-worker-prof
(5)parallel/test-runner-watch-mode
(4)wpt/test-timers
(4)parallel/test-http-request-join-authorization-headers
(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)sequential/test-perf-hooks
(2)The text was updated successfully, but these errors were encountered: