Output hash duplication detection fails fixed outputs (closes #697) #701
+7
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the output path to avoid repeating previously failued builds results to changes in fixed output paths not being rebuilt (e.g., updating a src url). Use the derivation path instead to fix this.
This seems to have resolved the issue on our hydra server (i.e., it now performs rebuilds even if only the source url is changed). I'm not an expert on this code base at all, so please do double check.
Here is a top-level example (usually this occurs on the
src
line for a package and not at top-level) of a package that exhibits the problem. Initially you havethen you realize the url has changed (or is wrong), so you update it to the correct one
but hydra doesn't rebuild it because both have the same fixed output path. With this patch it does rebuild because they don't both have the same drv path. Here is the test case I ran on our hydra server with this patch in place
Note, under the Details tab, how both builds have the same Output store paths.