Narrow better the inputs diff on build failed
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
For example, in http://hydra.nixos.org/build/5089682, something affected gcc 4.7 and made it fail.
Nevertheless, instead of showing the diff between 1) the last version of nixpkgs where gcc 4.7 built fine and the failing build, it shows 2) the last nixpkgs change that caused a succesful gcc rebuild and the failing nixpkgs. The 2) is over 250 changes, while 1) would be a very specific diff.
I thought I had file this issue before, but I can't find it now.
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
Reproduce the failed build at http://hydra.nixos.org/build/5089682 and inspect how Hydra selects the comparison builds for its inputs diff. Compare the current result with the last nixpkgs version where gcc 4.7 built successfully; done means the displayed diff is narrowed to that relevant range rather than more than 250 changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100