content_browsertests and chrome_public_test_apk are flaky on android-kitkat-arm-rel because of shard timeouts |
|||||
Issue descriptionA lot of tests are failing with "(status NOTRUN)" because of a shard timing out. Example: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-kitkat-arm-rel/164399 (shard #2 of chrome_public_test_apk timed out) https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-kitkat-arm-rel/164687 (shard #3 of content_browsertests timed out)
,
Jan 16
Issue 921999 has been merged into this issue.
,
Jan 16
Issue 921998 has been merged into this issue.
,
Jan 16
Issue 921997 has been merged into this issue.
,
Jan 16
Issue 921996 has been merged into this issue.
,
Jan 16
Issue 921995 has been merged into this issue.
,
Jan 16
Issue 921994 has been merged into this issue.
,
Jan 16
Issue 921993 has been merged into this issue.
,
Jan 16
Issue 921992 has been merged into this issue.
,
Jan 16
Issue 921991 has been merged into this issue.
,
Jan 16
Issue 921990 has been merged into this issue.
,
Jan 16
Issue 921989 has been merged into this issue.
,
Jan 16
Issue 921986 has been merged into this issue.
,
Jan 16
Issue 922003 has been merged into this issue.
,
Jan 16
Issue 921988 has been merged into this issue.
,
Jan 16
Issue 921977 has been merged into this issue.
,
Jan 16
Issue 921978 has been merged into this issue.
,
Jan 16
Issue 921979 has been merged into this issue.
,
Jan 16
Issue 921980 has been merged into this issue.
,
Jan 16
Issue 921981 has been merged into this issue.
,
Jan 16
Issue 921982 has been merged into this issue.
,
Jan 16
Issue 921985 has been merged into this issue.
,
Jan 16
Issue 804113 has been merged into this issue.
,
Jan 18
(4 days ago)
This seem like it's likely to be an infra issue?
,
Jan 18
(4 days ago)
At a glance, this just looks like tests failing slowly and causing the shard timeout. #24: what makes you think this is an infra issue?
,
Jan 18
(4 days ago)
I'm not sure that it's infra-related, but I am not convinced that it's just tests failing slowly either. For the chrome_public_test_apk failure, several test failures take the form: Deferred startup never completed or waitForCallback timed out (https://chromium-swarm.appspot.com/task?id=426b2c3568247010&refresh=10&show_raw=1) For the content_browsertests failure, none of the tests that were run actually failed. The shard times out because it spends 40 minutes(across two blocks) doing the following: Still working on StartInstrumentation [...] (https://chromium-swarm.appspot.com/task?id=426c16a406770610&refresh=10&show_raw=1) There seems to be an existing issue for the browsertests failure: https://crbug.com/836460
,
Jan 19
(4 days ago)
Given that, please continue to investigate this as a test failure; troopers don't really have the bandwidth to dig into test failures like this w/o some evidence that it's infra-related.
,
Jan 19
(4 days ago)
As for content_browsertests: that's part of the shard that's timing out.
,
Jan 19
(4 days ago)
Never mind; the task histories of the devices involved looks pretty questionable, h/t bpastene.
,
Jan 19
(4 days ago)
A (now deleted) bot also had a questionable history running the same tests back in 2018: https://chromium-swarm.appspot.com/bot?id=build259-m1--device4&sort_stats=total%3Adesc |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ksakamoto@chromium.org
, Jan 16