8000 Enable incompatible_use_specific_tool_files in bazel tests. · coderabbit-test/bazel@68277b3 · GitHub
[go: up one dir, main page]

Skip to content

Commit 68277b3

Browse files
Googlercopybara-github
authored andcommitted
Enable incompatible_use_specific_tool_files in bazel tests.
This has been enabled by default for a long time, but some tests still disable it. PiperOrigin-RevId: 746195596 Change-Id: I5c8bed08ffc13b7d0f3ef662f335cd74a05da2ee
1 parent da2c551 commit 68277b3

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

src/test/java/com/google/devtools/build/lib/buildtool/util/BuildIntegrationTestCase.java

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -670,8 +670,6 @@ protected void setupOptions() throws Exception {
670670
runtimeWrapper.addOptions("--experimental_extended_sanity_checks");
671671
runtimeWrapper.addOptions(TestConstants.PRODUCT_SPECIFIC_FLAGS);
672672
runtimeWrapper.addOptions(TestConstants.PRODUCT_SPECIFIC_BUILD_LANG_OPTIONS);
673-
// TODO(rosica): Remove this once g3 is migrated.
674-
runtimeWrapper.addOptions("--noincompatible_use_specific_tool_files");
675673

676674
if (AnalysisMock.get().isThisBazel()) {
677675
// We have to explicitly override @bazel_tools to the version in the workspace (which is where

0 commit comments

Comments
 (0)
0