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/64050 to node-test-pull-request/64147 that failed 2 or more PRs (Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-22.md)
ncu-ci walk pr --stats=true --markdown reports/2024-12-22.md
Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-22.md to see failure details
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
parallel/test-watch-file-shared-dependency
sequential/test-worker-prof
sequential/test-http-server-request-timeouts-mixed
parallel/test-net-write-fully-async-buffer
parallel/test-stream-readable-unpipe-resume
es-module/test-wasm-web-api
node-api/test_worker_buffer_callback/test-free-called
parallel/test-file-write-stream4
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Failures in node-test-pull-request/64050 to node-test-pull-request/64147 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown reports/2024-12-22.md)Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-22.md to see failure details
Progress
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(7)parallel/test-watch-file-shared-dependency(8)sequential/test-worker-prof(5)sequential/test-http-server-request-timeouts-mixed(4)parallel/test-net-write-fully-async-buffer(3)parallel/test-stream-readable-unpipe-resume(3)es-module/test-wasm-web-api(2)node-api/test_worker_buffer_callback/test-free-called(2)parallel/test-file-write-stream4(2)The text was updated successfully, but these errors were encountered: