Disable C++ toolchain resolution in Tulsi end-to-end tests
The mocks for C++ toolchain resolution are complex.
PiperOrigin-RevId: 508356482
diff --git a/src/TulsiGeneratorIntegrationTests/BazelIntegrationTestCase.swift b/src/TulsiGeneratorIntegrationTests/BazelIntegrationTestCase.swift
index e52a7d0..df3eef1 100644
--- a/src/TulsiGeneratorIntegrationTests/BazelIntegrationTestCase.swift
+++ b/src/TulsiGeneratorIntegrationTests/BazelIntegrationTestCase.swift
@@ -63,6 +63,10 @@
// Source is being copied outside of the normal workspace, so status commands won't work.
bazelBuildOptions.append("--workspace_status_command=/usr/bin/true")
+ // Integration tests is missing mocks for C++ toolchain resolution
+ // TODO(b/225026735): Remove after C++ toolchains are correctly mocked
+ bazelBuildOptions.append("--noincompatible_enable_cc_toolchain_resolution")
+
// Prevent any custom --bazelrc startup option to be specified. It should always be /dev/null.
for startupOption in bazelStartupOptions {
if (startupOption.hasPrefix("--bazelrc") && startupOption != "--bazelrc=/dev/null") {
