-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Delay invalidating cache and gcroots until print-dev-env call succeeds #420
Conversation
I haven't looked into test failures, but will when I find a moment. |
@mergify queue |
🛑 The pull request has been removed from the queue
|
@bbenne10 I get the same errors locally. Presumably only present after doing the rebase? |
We currently eagerly invalidate the gcroots and old profile rc, assuming that the devshell is in a usable state. If this assumption does not hold, we can invalidate a working state for a broken one. Here we just delay calling _nix_clean_old_gcroots until we know that we're in a usable state. In the case that the flake is in an unusable state, this simply reuses the newest working state. This should address #412.
I am starting to believe that there's something going wrong with the interaction between the creation of the I'm looking into it a bit more deeply now. |
Of course, I post and then figure out the bug.
|
213ed4a
to
494a0f1
Compare
494a0f1
to
c222894
Compare
There we go. Tests are passing now. I have rebased on #427 to keep in line with the logic and logging changes in there. We should get that merged first. |
@mergify queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at adeced7 |
We currently eagerly invalidate the gcroots and old profile rc, assuming that the devshell is in a usable state.
If this assumption does not hold,
we can invalidate a working state for a broken one.
Here we just delay calling
_nix_clean_old_gcroots
until we know that we're in a usable state.
In the case that the flake is in an unusable state, this simply reuses the latest working state.
This should address #412.