Disable MediaEngagementServiceTest.CleanUpDatabaseWhenHistoryIsExpired

This test is flaky on Linux and Android. See linked bug for details.

TBR=mlamouri@chromium.org

Bug: 1042417
Change-Id: I9a523e646973a9ce4efb578eff74c7e1961ea099
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026188Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736151}

chrome/browser/media/media_engagement_service_unittest.cc

@@ -586,7 +586,15 @@ TEST_P(MediaEngagementServiceTest, CleanupOriginsOnHistoryDeletion) {
   }
 }
 
-TEST_P(MediaEngagementServiceTest, CleanUpDatabaseWhenHistoryIsExpired) {
+// The test is flaky: crbug.com/1042417.
+#if defined(OS_LINUX) || defined(OS_ANDROID)
+#define MAYBE_CleanUpDatabaseWhenHistoryIsExpired \
+  DISABLED_CleanUpDatabaseWhenHistoryIsExpired
+#else
+#define MAYBE_CleanUpDatabaseWhenHistoryIsExpired \
+  CleanUpDatabaseWhenHistoryIsExpired
+#endif
+TEST_P(MediaEngagementServiceTest, MAYBE_CleanUpDatabaseWhenHistoryIsExpired) {
   // |origin1| will have history that is before the expiry threshold and should
   // not be deleted. |origin2| will have history either side of the threshold
   // and should also not be deleted. |origin3| will have history before the