New issue
Advanced search Search tips

Issue 742703 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
bsheedy@chromium.org
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug
Proj-XR
Proj-XR-VR



Sign in to add a comment

"org.chromium.chrome.browser.vr_shell.WebVrDeviceTest#testDeviceCapabilitiesMatchExpectations" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jul 14 2017 
"org.chromium.chrome.browser.vr_shell.WebVrDeviceTest#testDeviceCapabilitiesMatchExpectations" 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 9 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyZwsSBUZsYWtlIlxvcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIudnJfc2hlbGwuV2ViVnJEZXZpY2VUZXN0I3Rlc3REZXZpY2VDYXBhYmlsaXRpZXNNYXRjaEV4cGVjdGF0aW9ucww.

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

Comment 1 by fhorschig@chromium.org, Jul 14 2017

Cc: bsheedy@chromium.org jbudorick@chromium.org
Components: UI>Extensions>VR
Labels: Proj-VR Proj-VR-Shell
Status: Available (was: Untriaged)
Most of the WebVrDeviceTests seem flaky. Can we make the trybots happy by having a closer look at the waiting timeouts in all of these tests? Or should we disable them for even more versions?

(They used to be disabled for L, then updated for M -but without updating the comment - and now they are still flaking.)

Comment 2 by fhorschig@chromium.org, Jul 14 2017 

Another data point is  issue 742950 .

Comment 3 by bsheedy@chromium.org, Jul 14 2017 

Took a quick look, and the failures are being caused by native segfaults. That, combined with the fact that all WebVrDeviceTest#testDeviceCapabilitiesMatchExpectations does is load an HTML file that runs some JavaScript to interact with WebVR implies to me that some legitimate bug is being intermittently caught.

Comment 4 by jbudorick@chromium.org, Jul 14 2017 

given the timing, this is probably related to https://bugs.chromium.org/p/chromium/issues/detail?id=742463

Comment 5 by rogerta@chromium.org, Jul 17 2017 

 Issue 742950  has been merged into this issue.

Comment 6 by rogerta@chromium.org, Jul 17 2017

Labels: -Sheriff-Chromium
Status: WontFix (was: Available)
Given that this crash has not happened in the last 3 days and that the possible culprit mentioned in comment #4 was fixed, I am closing this bug.

Comment 7 by bsheedy@chromium.org, Mar 1 2018

Labels: VR-Caught-By-Test

Comment 8 by bsheedy@chromium.org, Aug 29

Labels: -VR-Caught-By-Test XR-Caught-By-Test
►

Sign in to add a comment