forked from bazelbuild/bazel
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BEP includes all files from successful actions in requested output gr…
…oups. As of ecd2a57 which fixed bazelbuild#9413, the BEP for failed builds will include output groups for which all files were successfully built. The expectation then was that files produced by successful actions during a build failure could be moved to different output group(s) where all files succeed. This has proven too optimistic, in particular when users define aspects applicable to all rule types. With this change, any files successfully produced for a requested output group will appear in the BEP, even if other files in the output group belonged to failed actions. RELNOTES: BEP includes all files from successful actions in requested output groups. Previously, an output group's files were excluded if any file in the output group was not produced due to a failing action. Users can expect BEP output to be larger for failed builds. PiperOrigin-RevId: 362289622
- Loading branch information
1 parent
b3ddeee
commit d2f93fd
Showing
4 changed files
with
426 additions
and
47 deletions.
There are no files selected for viewing
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
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
Oops, something went wrong.