DNL: Testing --remote_download_outputs=toplevel issue with Bazel 6.0.0rc1 & rc2 #618
Conversation
This file contains 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
gregmagolan
force-pushed
the
test_test
branch
from
d801982
to
976cad3
Compare
gregmagolan
changed the title
gregmagolan
force-pushed
the
test_test
branch
from
976cad3
to
84a4158
Compare
gregmagolan
changed the title
gregmagolan
force-pushed
the
test_test
branch
2 times, most recently
from
cb203ed
to
d70bd98
Compare
gregmagolan
force-pushed
the
test_test
branch
from
d70bd98
to
b1a8291
Compare
|
bazelbuild/bazel#16789 is the issue and fix should get into the 6.0.0 release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Based on testing it looks like the issue happens with
--remote_download_outputs=toplevelor--remote_download_outputs=minimalbut only with sandboxed execution and when there is a--disk_cacheor a--remote_cacheconfigured.The symptom seems to be that tree artifacts are just not present in the sandbox under these conditions. npm deps fail to resolve since the virtual store tree artifacts are not present.