components_unittests times out flakily on ios |
|||
Issue descriptionDetected 3 new flakes for test/step "components_unittests". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21wb25lbnRzX3VuaXR0ZXN0cww. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there). Two of the above flakes are due to some kind of timeout https://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/builds/138437 https://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/builds/138323 Error message: "shard #0 timed out, took too much time to complete" Output on chromium-swarm: Device wiped. /b/s/w/ir3ib3bU/src/out/Debug-iphonesimulator/iossim -d iPad Air 2 -s 10.0 /b/s/w/ir3ib3bU/src/out/Debug-iphonesimulator/components_unittests.app User defaults from command line: IDETestRunSpecificationPath = /var/folders/p4/py6nlvcx4fs5s3fg51_pzqmc0000gm/T/94B0CB9B-E41F-4399-A6B2-945CDDFFA79C As sheriff, I don't really know what to do with this other than file a bug about it... Peter, could you please take a look and assign appropriately?
,
Jan 18 2017
,
Jan 18 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by meade@chromium.org
, Jan 18 2017