We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Failures in node-test-pull-request/64498 to node-test-pull-request/64595 that failed 2 or more PRs (Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-22.md)
ncu-ci walk pr --stats=true --markdown reports/2025-01-22.md
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-22.md to see failure details
ERROR: Error fetching remote repo 'origin'
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Error: - process terminated with status 1, expected 0
Error: EBUSY: resource busy or locked, rmdir '\\?\C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638'
Error: EBUSY: resource busy or locked, rmdir '\\?\c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638'
fatal: Could not read from remote repository.
fatal: No rebase in progress?
parallel/test-http2-invalid-last-stream-id
sequential/test-http-server-request-timeouts-mixed
sequential/test-worker-prof
parallel/test-abortsignal-drop-settled-signals
parallel/test-net-write-fully-async-buffer
parallel/test-net-write-fully-async-hex-string
benchmark/test-benchmark-http2
node-api/test_threadsafe_function/test
parallel/test-buffer-tostring-range
parallel/test-http-get-pipeline-problem
parallel/test-http2-premature-close
parallel/test-without-async-context-frame
sequential/test-perf-hooks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Failures in node-test-pull-request/64498 to node-test-pull-request/64595 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown reports/2025-01-22.md)Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-22.md to see failure details
Progress
ERROR: Error fetching remote repo 'origin'(3)ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(6)Error: - process terminated with status 1, expected 0(2)Error: EBUSY: resource busy or locked, rmdir '\\?\C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638'(2)Error: EBUSY: resource busy or locked, rmdir '\\?\c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638'(2)fatal: Could not read from remote repository.(2)fatal: No rebase in progress?(2)parallel/test-http2-invalid-last-stream-id(4)sequential/test-http-server-request-timeouts-mixed(4)sequential/test-worker-prof(4)parallel/test-abortsignal-drop-settled-signals(3)parallel/test-net-write-fully-async-buffer(3)parallel/test-net-write-fully-async-hex-string(3)benchmark/test-benchmark-http2(2)node-api/test_threadsafe_function/test(2)parallel/test-buffer-tostring-range(2)parallel/test-http-get-pipeline-problem(2)parallel/test-http2-premature-close(2)parallel/test-without-async-context-frame(2)sequential/test-perf-hooks(2)The text was updated successfully, but these errors were encountered: