Previous Hydra evaluation doesn't work
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
When I use Previous Hydra evaluation as an input, it arrives with only subset of jobs in it and I see errors like:
in job ‘build’:
attribute 'my-app' missing, at [1m/nix/store/bhkvbl93hh6vgwqarcr6hks6qclimarc-source/nix/release.nix[0m:15:19
The evaluation should be like:
{
my-app = {
tarball = mkDerivation { ... };
}
package = mkDerivation { ... };
source = mkDerivation { ... };
}
Through experiments I've found that it has only package job in it. All others are lost. But they work flawlessly if I pass them individually as Previous Hydra builds.
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 issue using Previous Hydra evaluation and compare its jobs with individually supplied Previous Hydra builds. Start by tracing how the evaluation input is assembled around nix/release.nix; done means the evaluation preserves jobs such as my-app, package, and source without the reported missing-attribute errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100