Commit 34f6bd7e authored by Scott Graham's avatar Scott Graham Committed by Commit Bot

fuchsia: Disable some flaking tests in base, content, net

TBR: wez@chromium.org
Bug: 784448, 784449
Change-Id: I06d0473968ae2dbdb9c480cf58b25ba1fbc2a764
Reviewed-on: https://chromium-review.googlesource.com/766152Reviewed-by: default avatarScott Graham <scottmg@chromium.org>
Commit-Queue: Scott Graham <scottmg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#515979}
parent 976fe5f3
...@@ -40,6 +40,7 @@ ...@@ -40,6 +40,7 @@
# pretty confident you've fixed their rarely-flakiness before re-enabling. # pretty confident you've fixed their rarely-flakiness before re-enabling.
-AllModes/TaskSchedulerSingleThreadTaskRunnerManagerCommonTest.* -AllModes/TaskSchedulerSingleThreadTaskRunnerManagerCommonTest.*
-AllocationRegisterTest.InsertRemoveRandomOrder -AllocationRegisterTest.InsertRemoveRandomOrder
-ConditionVariableTest.MultiThreadConsumerTest
-MemoryPeakDetectorTest.StdDev -MemoryPeakDetectorTest.StdDev
-MemoryPeakDetectorTest.Throttle -MemoryPeakDetectorTest.Throttle
-ObserverListThreadSafeTest.CrossThreadObserver -ObserverListThreadSafeTest.CrossThreadObserver
......
...@@ -55,3 +55,6 @@ ...@@ -55,3 +55,6 @@
# Flaky: https://crbug.com/780508. # Flaky: https://crbug.com/780508.
-ServiceWorkerProviderHostTest.* -ServiceWorkerProviderHostTest.*
# Flaky, https://crbug.com/784449.
-WebContentsAudioInputStreamTest.MirroringOneStreamAfterTargetChange*
...@@ -14,3 +14,6 @@ ...@@ -14,3 +14,6 @@
# These stress tests take a very long time on emulated ARM cores. # These stress tests take a very long time on emulated ARM cores.
-SupportedVersion/QuicConnectionTest.TooManySentPackets/* -SupportedVersion/QuicConnectionTest.TooManySentPackets/*
-RangeOfTreeSizes/CTLogVerifierTestUsingGenerator.VerifiesValidConsistencyProof/* -RangeOfTreeSizes/CTLogVerifierTestUsingGenerator.VerifiesValidConsistencyProof/*
# Flaky, https://crbug.com/784448.
-DiskCacheBackendTest.InvalidEntry5
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment