Failure triage: an option to build on the base branch to compare failures
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Consider https://github.com/NixOS/nixpkgs/pull/34676 — I see some failures, I would like to say build-base-branch diffpdf to see if these are new or inherited (OK, on Darwin it is just meta.platforms, but it would be nice to check aarch64-linux).
Contributor guide
No contributing guide indexed for this repository
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 the referenced nixpkgs pull request and the build-base-branch diffpdf entry point; the payload names no files or tests. Define how the command should compare base-branch and current failures, then verify that it distinguishes inherited failures from new ones, including the mentioned aarch64-linux case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100