nodejs / nodejs/node-core-utils
Add list of errors to ignore when parsing for failure reason
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 314
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
In the reliability reports we see high counts of "fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository" but this is an error that should be ignored and it being reported is hiding whatever the real problem was.
It would be good if we could update the tooling to ignore specific errors like that.
@richardlau pointed to this area in the code as a place to start: https://github.com/nodejs/node-core-utils/blob/main/lib/ci/ci_failure_parser.js
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 lib/ci/ci_failure_parser.js, the area linked in the issue, and trace how failure reasons are extracted from reliability reports. Define how ignored error patterns should be represented and verify that the cited ccache Git error no longer hides the underlying failure reason.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100