nodejs / nodejs/node-core-utils
Inconsistent CI status
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 314
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
CI: https://ci.nodejs.org/job/node-test-pull-request/51006/ show failure.
But it has been resume build, https://ci.nodejs.org/job/node-test-commit/61403/ showed success.
https://ci.nodejs.org/job/node-test-pull-request/51006/ still linked to old https://ci.nodejs.org/job/node-test-commit/61376/
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 by comparing the linked pull-request build 51006 with commit builds 61403 and 61376, then inspect PR #46930 and the CI status handling in node-core-utils. Determine why the pull-request result remains linked to the older commit; done means the status reflects the resumed successful build consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100