CI Reliability 2026-02-27
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Failures in node-test-pull-request/71381 to node-test-pull-request/71474 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-02-27.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-02-27 00:17 | 0 | 16 | 35 | 5 | 44 | 16.84% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-02-27.md to see failure details
Progress
-
Failed to trigger node-test-commit(3) -
Error: 'utf-8' codec can't decode byte 0xc1 in position 243: invalid start byte(2) -
Failed to trigger sub builds(2) -
fatal: No rebase in progress?(2) -
async-hooks/test-emit-before-on-destroyed(3) -
parallel/test-async-context-frame(3) -
parallel/test-child-process-fork-exec-path(3) -
parallel/test-file-write-stream4(3) -
parallel/test-http-client-response-domain(3) -
parallel/test-module-loading-globalpaths(3) -
parallel/test-promise-reject-callback-exception(3) -
parallel/test-tls-dhe(3) -
wpt/test-hr-time(3) -
async-hooks/test-improper-order(2) -
parallel/test-async-hooks-http-parser-destroy(2) -
parallel/test-runner-run-watch(2) -
sea/test-build-sea(2) -
sea/test-build-sea-already-exists(2) -
sea/test-build-sea-custom-argv0(2) -
sea/test-build-sea-executable-field(2) -
sea/test-build-sea-missing-output(2) -
sea/test-single-executable-application-asset-keys(2) -
sea/test-single-executable-application-asset-keys-empty(2) -
sea/test-single-executable-application-assets(2) -
sea/test-single-executable-application-assets-raw(2) -
sea/test-single-executable-application-disable-experimental-sea-warning(2) -
sea/test-single-executable-application-empty(2) -
sea/test-single-executable-application-esm(2) -
sea/test-single-executable-application-exec-argv(2) -
sea/test-single-executable-application-exec-argv-extension-cli(2) -
sequential/test-performance-eventloopdelay(2)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with reports/2026-02-27.md and the linked node-test-pull-request builds 71381–71474. Review the listed trigger, encoding, rebase, and test failures to determine which failures are actionable. Done means the causes are investigated and the progress items have been resolved or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100