Fix additional outputs in BEP when remote_download_minimal is used#15711
Fix additional outputs in BEP when remote_download_minimal is used#15711exoson wants to merge 1 commit intobazelbuild:masterfrom
Conversation
|
Will be fixing the tests later. Would appreciate comments on if a change along these lines would make sense. |
Injects optional test outputs when using --remote_download_minimal and uses the list of injected artifacts to list them in BEP TestResult.
18d800c to
24e567e
Compare
|
Thanks for your PR! Since this PR is mainly about test strategy and is already beyond my limited understanding of it, I will try to find an appropriate reviewer. Out of my head, are these additional outputs already referenced in BEP for normal build / remote build? |
Yes, the files are currently referenced as long as the files exist under bazel-testlogs. With |
|
@coeuvre Any updates on finding a reviewer? |
|
I went with another way (#16123) to fix this issue. It requires no changes outside remote module and allow us to remove the hack in |
Thanks! I'll close this PR. |
So that spawn outputs can be accessed among Spwans within the same action using the `FileSystem` API. This allow us to revert the hack we introduced in #12590. Also fixes the issue described by #15711. Closes #15711. Closes #16123. PiperOrigin-RevId: 469133936 Change-Id: Ide5bcfa0fe2c6a3806d333cd61270e411aa78f80
So that spawn outputs can be accessed among Spwans within the same action using the `FileSystem` API. This allow us to revert the hack we introduced in bazelbuild#12590. Also fixes the issue described by bazelbuild#15711. Closes bazelbuild#15711. Closes bazelbuild#16123. PiperOrigin-RevId: 469133936 Change-Id: Ide5bcfa0fe2c6a3806d333cd61270e411aa78f80
Injects optional test outputs when using --remote_download_minimal and
uses the list of injected artifacts to list them in BEP TestResult.