Evaluate with aliases enabled additionally
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 322
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/NixOS/nixpkgs/pull/349431/ https://github.com/NixOS/nixpkgs/pull/349783 show that changes to aliases can break evaluation of nixpkgs with aliases enabled while not affecting it with aliases disabled. Almost all downstream users will probably have aliases enabled, so this is a situation we should ideally check for. Saving grace is probably that most Hydra jobsets have aliases enabled.
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 by reading the issue and the referenced nixpkgs pull requests #349431 and #349783 to understand the alias-related evaluation failures. Then locate the evaluation configuration in ofborg; done means aliases-enabled evaluation is checked in addition to the existing mode and can detect regressions that aliases-disabled evaluation misses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100