build257-m1--device2 frequently failing / timing out on tests |
|||||||
Issue description"content_shell_test_apk (with patch)" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLgsSBUZsYWtlIiNjb250ZW50X3NoZWxsX3Rlc3RfYXBrICh3aXRoIHBhdGNoKQw. The chromium-try-flakes app is able to file bugs for individual tests when the test launcher is uploading results to the Test Results Server. If recent flakes above are caused by failing tests and you would like to have them filed as invidual bugs, please read more at https://goo.gl/QJKXV4. This flaky test/step was previously tracked in issue 625584 .
,
Dec 28 2017
Device screen is off. I see the following error: java.lang.AssertionError: Many tests will fail if the screen is not on. at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.chromium.content_shell_apk.ContentShellTestCommon.assertScreenIsOn(ContentShellTestCommon.java:70) at org.chromium.content_shell_apk.ContentShellActivityTestRule.beforeActivityLaunched(ContentShellActivityTestRule.java:59) at android.support.test.rule.ActivityTestRule.launchActivity(ActivityTestRule.java:216) at org.chromium.content_shell_apk.ContentShellActivityTestRule.launchActivityWithIntentForTestCommon(ContentShellActivityTestRule.java:194) at org.chromium.content_shell_apk.ContentShellActivityTestRule.launchActivityWithIntentForTestCommon(ContentShellActivityTestRule.java:40) at org.chromium.content_shell_apk.ContentShellTestCommon.launchContentShellWithUrl(ContentShellTestCommon.java:82) at org.chromium.content_shell_apk.ContentShellTestCommon.launchContentShellWithUrlSync(ContentShellTestCommon.java:88) at org.chromium.content_shell_apk.ContentShellActivityTestRule.launchContentShellWithUrlSync(ContentShellActivityTestRule.java:78)
,
Dec 28 2017
This appears to be an issue w/ https://chromium-swarm.appspot.com/bot?id=build257-m1--device2 specifically.
,
Dec 28 2017
Drained the device's container.
,
Dec 28 2017
Hunting for a hammerhead flash isolate to reflash this device.
,
Jan 3 2018
I'm guessing you couldn't find one. I'll document the whole process someday... In the meantime I triggered a flash: https://chromium-swarm.appspot.com/task?id=3ad6120757216710
,
Jan 3 2018
correct, despite digging through your (somewhat recent) swarming task history. only bullheads.
,
Jan 3 2018
Nope; reflash didn't help. It's still timing out tests. Back into the scrapheap that phone goes.
,
Jan 3 2018
hrm. Too bad it's in the golo, it'd be interesting to see what's going on. Thanks for flashing it, though. Dropping to available, as I'm not actively working on this at the moment given that we've got the phone out of the pool.
,
Jan 4
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 7
I think this is no longer relevant, the bot hasn't had any events in ~1 year and is reported as deleted. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by sergeyu@chromium.org
, Dec 28 2017