Disable test that flakily fails in Linux component builds

Locally I did a release+component build and this test failed 65 out of
100 local runs.

TBR=msramek@chromium.org

Bug: 985131
Change-Id: Iff5d243e6adeb198939bc8e7699879bcc85ab668
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1707571Reviewed-by: Reid Kleckner <rnk@chromium.org>
Commit-Queue: Reid Kleckner <rnk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#678494}

chrome/browser/browsing_data/counters/cache_counter_browsertest.cc

@@ -174,9 +174,16 @@ IN_PROC_BROWSER_TEST_F(CacheCounterTest, AfterDoom) {
   EXPECT_EQ(0u, GetResult());
 }
 
+// TODO(crbug.com/985131): Test is flaky in Linux component builds.
+#if defined(OS_LINUX) && defined(COMPONENT_BUILD)
+#define MAYBE_PrefChanged DISABLED_PrefChanged
+#else
+#define MAYBE_PrefChanged PrefChanged
+#endif
+
 // Tests that the counter starts counting automatically when the deletion
 // pref changes to true.
-IN_PROC_BROWSER_TEST_F(CacheCounterTest, PrefChanged) {
+IN_PROC_BROWSER_TEST_F(CacheCounterTest, MAYBE_PrefChanged) {
   SetCacheDeletionPref(false);
 
   Profile* profile = browser()->profile();