"org.chromium.chrome.browser.vr_shell.WebVrDeviceTest#testGvrlessMagicWindowCapabilities__ChromeTabbedActivity" is flaky |
||||
Issue description"org.chromium.chrome.browser.vr_shell.WebVrDeviceTest#testGvrlessMagicWindowCapabilities__ChromeTabbedActivity" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyeAsSBUZsYWtlIm1vcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIudnJfc2hlbGwuV2ViVnJEZXZpY2VUZXN0I3Rlc3RHdnJsZXNzTWFnaWNXaW5kb3dDYXBhYmlsaXRpZXNfX0Nocm9tZVRhYmJlZEFjdGl2aXR5DA. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Apr 19 2018
I'll take a look later today.
,
Apr 19 2018
This looks like a device issue, not an issue with the test. This only occurs on build91-b4--device5. The test is failing due to not getting a VRDisplay, which should only happen for this test if sensors (gyroscope/accelerometer) are unavailable, so it looks like build91-b4--device5 is starting to go bad. +cc bpastene@ - Ben, should the device just be removed, or do you think it's worth investigating it further? I'm not sure how common gyroscope failure is on the swarming bots.
,
Apr 19 2018
Gyroscope failure? Cooool... Our phones are always finding new ways to fail. I'll trigger a reflash in the off-chance that whatever's wrong with it can be cured with a clean system image. If that doesn't help things, I'll take it offline. Do you know if there's an easy one/two liner adb command we can run to detect these types of failures programmatically? If not, then I'd say let's just trash the phone and move on.
,
Apr 19 2018
I'd have to try it out myself, but maybe reading the raw data from the sensors like in https://stackoverflow.com/questions/33525142/recycling-sensors-from-a-broken-android-device-using-adb ?
,
Apr 20 2018
,
Apr 20 2018
After reflashing, the bot took another chrome_public_test_vr task and succeeded: https://chromium-swarm.appspot.com/task?id=3cf867c741e32710 Looks like testGvrlessMagicWindowCapabilities__ChromeTabbedActivity passed. Maybe the reflash healed it? Might have to wait for it to pick up a few more vr tests to confirm
,
Apr 23 2018
Haven't seen any failures since the reflash. I think it's safe to say it's fixed. |
||||
►
Sign in to add a comment |
||||
Comment 1 by mstensho@chromium.org
, Apr 19 2018Status: Assigned (was: Untriaged)