Commit 7533c1f9 authored by Makoto Shimazu's avatar Makoto Shimazu Committed by Commit Bot

Disable a test in WizardControllerDeviceStateWithInitialEnrollmentTest

WizardControllerDeviceStateWithInitialEnrollmentTest.ControlFlowWaitSystemClockSyncTimeout
is now flaky. It seems affected by crrev.com/c/1118532, but that CL just added
some CHECKs to check if it's not captured by ThreadTaskRunnerHandle. I think we
need to keep the task runner properly.

TBR=jdufault@chromium.org
NOTRY=true

Bug: 860092
Change-Id: Id7e566d4a48f59e2f2b7121c0875afcd9dc09b24
Reviewed-on: https://chromium-review.googlesource.com/1125554Reviewed-by: default avatarMakoto Shimazu <shimazu@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#572471}
parent e1653873
......@@ -1619,8 +1619,9 @@ IN_PROC_BROWSER_TEST_F(WizardControllerDeviceStateWithInitialEnrollmentTest,
5 /* NotRequiredInEmbargoPeriod*/, 1 /* count */);
}
// Disabled because it's flaky: crbug.com/860092.
IN_PROC_BROWSER_TEST_F(WizardControllerDeviceStateWithInitialEnrollmentTest,
ControlFlowWaitSystemClockSyncTimeout) {
DISABLED_ControlFlowWaitSystemClockSyncTimeout) {
auto task_runner = base::MakeRefCounted<base::TestMockTimeTaskRunner>();
base::TestMockTimeTaskRunner::ScopedContext scoped_context(task_runner);
......
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