From b2f53e0cde6c1e3fff0d6ee5030ef55bc4ffc48d Mon Sep 17 00:00:00 2001
From: Polina Cherkasova <polinach@google.com>
Date: Thu, 4 Jan 2024 11:32:17 -0800
Subject: [PATCH] Temporarily remove env variable for leak tracking bots.
 (#140978)

For some reasons there are [failures](https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8759809744202981089/+/u/run_test.dart_for_framework_tests_shard_and_subshard_misc/test_stdout) in leak tracking bots, that do not relate to leak tracking.

There are two differences between leak tracking bots and 'normal' windows framework bots:

1. The flag "LEAK_TRACKING": "true". First failures happened before consumption of the flag "LEAK_TRACKING": "true" by testWidgets. Hypothesis: the failures may be caused by mechanisms that sets the env variable. This mechanism is used only by leak tracking bots.
2. bringup: true.

This PR removes the leak tracking env variable to isolate the first difference and verify if the bots will start passing.
---
 .ci.yaml | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/.ci.yaml b/.ci.yaml
index 78d924b7f25..0e714e6e3d8 100644
--- a/.ci.yaml
+++ b/.ci.yaml
@@ -4974,10 +4974,6 @@ targets:
       subshard: libraries
       tags: >
         ["framework", "hostonly", "shard", "windows"]
-      env_variables: >-
-        {
-          "LEAK_TRACKING": "true"
-        }
     runIf:
       - dev/**
       - packages/flutter/**
@@ -5036,10 +5032,6 @@ targets:
       subshard: misc
       tags: >
         ["framework", "hostonly", "shard", "windows"]
-      env_variables: >-
-        {
-          "LEAK_TRACKING": "true"
-        }
     runIf:
       - dev/**
       - examples/api/**
@@ -5092,10 +5084,6 @@ targets:
       subshard: widgets
       tags: >
         ["framework", "hostonly", "shard", "windows"]
-      env_variables: >-
-        {
-          "LEAK_TRACKING": "true"
-        }
     runIf:
       - dev/**
       - packages/flutter/**