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.
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
Unify sandbox/remote handling of empty TreeArtifact inputs #15276
Unify sandbox/remote handling of empty TreeArtifact inputs #15276
Changes from all commits
ab82887
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get why this is removed. Can you explain a bit more?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function is passed the expanded coverage dir
TreeArtifact
inexpandedCoverageDir
and adds the contained files to the spawn inputs. In addition, it also used to add theTreeArtifact
itself, which doesn't really make sense to me: EitherSpawnInputExpander
can expand theTreeArtifact
, in which case expanding it manually wouldn't be necessary here, or it can't, in which case it would expand to nothing just like an emptyTreeArtifact
prior to this change.It turns out that the latter is the case: For some reason beyond my understanding, the coverage directory
TreeArtifact
is created in a way so thatSpawnInputExpander
fails to see as non-empty, butbazel/src/main/java/com/google/devtools/build/lib/exec/StandaloneTestStrategy.java
Line 834 in 5343d7c
Since the coverage script creates the coverage directory anyway in
bazel/tools/test/collect_coverage.sh
Line 75 in f2a7475
The commit that introduced the coverage directory
TreeArtifact
expansion logic is a445cda. If you would like a better explanation for why this artifact can't be expanded in the usual way, I could ping the author.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see.
SpawnInputExpander
can only expand inputs which are existing prior to action execution. This post-processing spawn is collecting inputs generated by previous spawn which are not visible toSpawnInputExpander
so it is always expand to nothing -- that's the reason why we manually expand tree artifact here by reading directly from metadata provider.I think it's safe to remove this line here. but @oquenchil can you confirm since you originally wrote this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it looks safe to me.