Remove dead code in thinlto test.

The call to AnalysisMock in testFdoNoImplicitThinLto is unnecessary since the following call to setupFdoThinLtoCrosstool overrides the features. Tested: Existing unit tests pass with the code removed. PiperOrigin-RevId: 351107596
comius · Jan 11, 2021 · 30ceb80 · 30ceb80
1 parent 8720ff4
commit 30ceb80
Showing 1 changed file with 0 additions and 6 deletions.
diff --git a/src/test/java/com/google/devtools/build/lib/rules/cpp/CcBinaryThinLtoTest.java b/src/test/java/com/google/devtools/build/lib/rules/cpp/CcBinaryThinLtoTest.java
@@ -1396,12 +1396,6 @@ private void setupFdoThinLtoCrosstool() throws Exception {
    */
   @Test
   public void testFdoNoImplicitThinLto() throws Exception {
-    AnalysisMock.get()
-        .ccSupport()
-        .setupCcToolchainConfig(
-            mockToolsConfig,
-            CcToolchainConfig.builder()
-                .withFeatures(CppRuleClasses.THIN_LTO, CppRuleClasses.SUPPORTS_START_END_LIB));
     scratch.file(
         "pkg/BUILD",
         "",