-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Do not clear --platforms
on no-op change to --cpu
#17158
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
Conversation
Due to a Bazel issue (bazelbuild/bazel#17158), the recent introduction of `universal_binary` ended up forking the configuration for dependencies of the Jazzer launcher. As a result, some Java targets were built twice and the Docker images failed to build as the Jazzer standalone jar was no longer a dependency of the launcher in the default configuration. As a workaround and also because it prevents similar issues on a more fundamental level, switch to the soon to be default improved config hash algorithm.
@gregestren Could you take a look? This resolves a build time regressions we had when we picked up rules_apple's |
Resolves a TODO in the code to not unnecessarily fork the configuration when a transition has `--cpu` as a declared output but doesn't change it.
7a65c45
to
57fc3d2
Compare
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.
LGTM, just a few small changes I'd like to request.
.build() | ||
: originalOutput; | ||
BuildOptions options, Map<String, Object> originalOutput) { | ||
Object newCpu = originalOutput.get(COMMAND_LINE_OPTION_PREFIX + "cpu"); |
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.
Nit: The names newCpu
and originalOutput
don't seem to match. Can we rename one of them?
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.
Done, renamed the existing variable to be more descriptive.
src/test/java/com/google/devtools/build/lib/analysis/StarlarkAttrTransitionProviderTest.java
Show resolved
Hide resolved
src/test/java/com/google/devtools/build/lib/analysis/StarlarkAttrTransitionProviderTest.java
Show resolved
Hide resolved
Due to a Bazel issue (bazelbuild/bazel#17158), the recent introduction of `universal_binary` ended up forking the configuration for dependencies of the Jazzer launcher. As a result, some Java targets were built twice and the Docker images failed to build as the Jazzer standalone jar was no longer a dependency of the launcher in the default configuration. As a workaround and also because it prevents similar issues on a more fundamental level, switch to the soon to be default improved config hash algorithm.
@bazel-io flag |
@bazel-io fork 6.1.0 |
Resolves a TODO in the code to not unnecessarily fork the configuration when a transition has `--cpu` as a declared output but doesn't change it. Closes #17158. PiperOrigin-RevId: 501021431 Change-Id: Ib942ea9584b2ceb3083b5fec71e2e11b89dcfdb6 Co-authored-by: Fabian Meumertzheim <[email protected]>
Resolves a TODO in the code to not unnecessarily fork the configuration when a transition has `--cpu` as a declared output but doesn't change it. Closes #17158. PiperOrigin-RevId: 501021431 Change-Id: Ib942ea9584b2ceb3083b5fec71e2e11b89dcfdb6
Resolves a TODO in the code to not unnecessarily fork the configuration when a transition has
--cpu
as a declared output but doesn't change it.