Generate both real and smoke manifests before pruning #31
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm not obviously seeing the CI breakage in the diff. r=me with CI fixed unless you make some major changes and want a re-review. |
|
Broken CI is fixed by #32. |
|
#32 landed; is there anything else blocking this PR? |
|
Beta CI is still broken until the beta promotion lands. |
pietroalbini
force-pushed
the
fix-miri
branch
from
efa792d to
cd4ddae
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR fixes #30 by generating all the manifests before the pruning step happens, granting access to
toolstates-linux.jsonto the "real"build-manifestinvocation.r? @Mark-Simulacrum