Disable IndexedDBExecutionContextConnectionTrackerBrowserTest.ObserverTwoLocks

Disable it on ChromeOS release builds for being flaky.

TBR=dmurph

Bug: 1030733
Change-Id: I44db0ed9e8fce4c94d5e4833b2a88666c63eb27b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1951084
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721560}

content/browser/indexed_db/indexed_db_execution_context_connection_tracker_browsertest.cc

@@ -191,8 +191,14 @@ IN_PROC_BROWSER_TEST_F(IndexedDBExecutionContextConnectionTrackerBrowserTest,
 // Verify that content::LockObserver is notified when a frame opens multiple
 // IndexedDB connections (notifications only when the number of held connections
 // switches between zero and non-zero).
+// Disabled on ChromeOS release build for flakiness. See crbug.com/1030733.
+#if defined(OS_CHROMEOS) && defined(NDEBUG)
+#define MAYBE_ObserverTwoLocks DISABLED_ObserverTwoLocks
+#else
+#define MAYBE_ObserverTwoLocks ObserverTwoLocks
+#endif
 IN_PROC_BROWSER_TEST_F(IndexedDBExecutionContextConnectionTrackerBrowserTest,
-                       ObserverTwoLocks) {
+                       MAYBE_ObserverTwoLocks) {
   if (!CheckShouldRunTestAndNavigate())
     return;