Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the detection of already built drv outputs #4378

Merged
merged 1 commit into from Dec 17, 2020
Merged

Conversation

thufschmitt
Copy link
Member

PRs #4370 and #4348 had a bad interaction in that the second broke the fist
one in a not trivial way.

The issue was that since #4348 the logic for detecting whether a
derivation output is already built requires some logic that was specific
to the LocalStore.

It happens though that most of this logic could be upstreamed to any Store,
which is what this commit does.

PRs #4370 and #4348 had a bad interaction in that the second broke the fist
one in a not trivial way.

The issue was that since #4348 the logic for detecting whether a
derivation output is already built requires some logic that was specific
to the `LocalStore`.

It happens though that most of this logic could be upstreamed to any `Store`,
which is what this commit does.
@thufschmitt thufschmitt added this to the ca-derivations-mvp milestone Dec 17, 2020
@thufschmitt thufschmitt added ca-derivations Derivations with content addressed outputs bug and removed ca-derivations Derivations with content addressed outputs labels Dec 17, 2020
@thufschmitt
Copy link
Member Author

As a nice side effect, this also makes this detection logic also work with non-ca derivations

@edolstra edolstra merged commit 26e189c into master Dec 17, 2020
@edolstra edolstra deleted the fix-master-build branch December 17, 2020 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants