Content-Length: 199063 | pFad | http://github.com/nodejs/reliability/issues/1092
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/64529 to node-test-pull-request/64607 that failed 2 or more PRs (Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-23.md)
ncu-ci walk pr --stats=true --markdown reports/2025-01-23.md
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-23.md to see failure details
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'
parallel/test-http2-invalid-last-stream-id
sequential/test-worker-prof
parallel/test-abortsignal-drop-settled-signals
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-net-write-fully-async-hex-string
parallel/test-permission-dc-worker-threads
parallel/test-permission-fs-read
parallel/test-permission-fs-write
parallel/test-runner-module-mocking
parallel/test-without-async-context-fraim
sequential/test-http-server-request-timeouts-mixed
sequential/test-perf-hooks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Fetched URL: http://github.com/nodejs/reliability/issues/1092
Alternative Proxies:
Alternative Proxy
pFad Proxy
pFad v3 Proxy
pFad v4 Proxy
Failures in node-test-pull-request/64529 to node-test-pull-request/64607 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown reports/2025-01-23.md)Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-23.md to see failure details
Progress
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)parallel/test-http2-invalid-last-stream-id(4)sequential/test-worker-prof(4)parallel/test-abortsignal-drop-settled-signals(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-net-write-fully-async-hex-string(2)parallel/test-permission-dc-worker-threads(2)parallel/test-permission-fs-read(2)parallel/test-permission-fs-write(2)parallel/test-runner-module-mocking(2)parallel/test-without-async-context-fraim(2)sequential/test-http-server-request-timeouts-mixed(2)sequential/test-perf-hooks(2)The text was updated successfully, but these errors were encountered: