Re-enable ios_web_inttests |
|||
Issue descriptionEnabling ios_web_inttests downstream made the bot extremely flaky. The failures are "shard #0 timed out, took too much time to complete" https://touch-swarming.appspot.com/task?id=3608eacbdeccda10&refresh=10&show_raw=1 https://uberchromegw.corp.google.com/i/internal.bling.main/builders/iphone10-device-x64/builds/4960 I have reverted the CL enabling them.
,
May 10 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/c4836001223cc6a6dba4bcdfce42b00e72af51ef commit c4836001223cc6a6dba4bcdfce42b00e72af51ef Author: eugenebut <eugenebut@google.com> Date: Wed May 10 14:51:46 2017
,
May 10 2017
Gauthier, the tests run fine on FYI without flakes and failures. When I put them yesterday on the main waterfall, they were failing till 9PM PST, until I disabled WebUIMojoTest.MessageExchange. In your link the only failure I see was WebUIMojoTest.MessageExchange. Did you see any other flakes/failures?
,
May 10 2017
I have seen HistoryStateOperationsTest.StateReplacementReload several times. https://touch-swarming.appspot.com/task?id=3609dc793f2e8710&refresh=10&show_raw=1
,
May 10 2017
Thanks! I will also disable HistoryStateOperationsTest.StateReplacementReload and will keep looking at FYI.
,
May 10 2017
,
May 15 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by eugene...@chromium.org
, May 10 2017Labels: -Restrict-View-Google -Type-Bug Type-Task
Status: Started (was: Assigned)