-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Disable --legacy_external_runfiles
in Bazel tests
#20680
Conversation
d5e9156
to
733f4c9
Compare
--legacy_external_runfiles
--legacy_external_runfiles
in Bazel tests
733f4c9
to
bb7fd4f
Compare
bb7fd4f
to
ec2ebba
Compare
I support this pending an answer to #12821 (comment) . |
ec2ebba
to
2119cf2
Compare
Prepares for the flip (bazelbuild#12821) by ensuring that Bazel itself doesn't regress.
2119cf2
to
666e2a5
Compare
@lberki A rebase fixed all test failures. Given that we can't go back to just the |
I support the idea. @Wyverald WDYT? (I don't want to just reach over his head) |
@bazel-io fork 7.1.0 |
This requires fixing an actual bug that causes the Windows Java launcher to not find the Java runtime with `--nolegacy_external_runfiles`. Work towards bazelbuild#12821 Closes bazelbuild#20680. PiperOrigin-RevId: 601826685 Change-Id: Ib45e60901d47efc06bf875c334edafcaeabc5f1e
This requires fixing an actual bug that causes the Windows Java launcher to not find the Java runtime with `--nolegacy_external_runfiles`. Work towards #12821 Closes #20680. Commit 3d4491c PiperOrigin-RevId: 601826685 Change-Id: Ib45e60901d47efc06bf875c334edafcaeabc5f1e Co-authored-by: Fabian Meumertzheim <[email protected]>
The changes in this PR have been included in Bazel 7.1.0 RC1. Please test out the release candidate and report any issues as soon as possible. If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc. |
This requires fixing an actual bug that causes the Windows Java launcher to not find the Java runtime with
--nolegacy_external_runfiles
.Work towards #12821