New issue
Advanced search Search tips

Issue 881749 link

Starred by 1 user
Status: WontFix
Owner:
bsheedy@chromium.org
Closed: Sep 12
Cc:
bpastene@chromium.org
peconn@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

WebXrVr tests failing on Marshmallow 64 bit Tester

Project Member Reported by peconn@chromium.org, Sep 7 
Example failures:
  https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Marshmallow%2064%20bit%20Tester/23703

The following tests failed:
org.chromium.chrome.browser.vr.WebXrVrTransitionTest#testRequestPresentEntersVr__CustomTabActivity
org.chromium.chrome.browser.vr.WebXrVrInputTest#testScreenTapsRegisteredOnCardboard_WebXr__CustomTabActivity
org.chromium.chrome.browser.vr.WebXrVrTransitionTest#testRequestPresentEntersVr__WebappActivity
org.chromium.chrome.browser.vr.WebXrVrTransitionTest#testNonImmersiveStopsDuringImmersive__CustomTabActivity
org.chromium.chrome.browser.vr.WebXrVrTransitionTest#testRequestSessionEntersVr__ChromeTabbedActivity
org.chromium.chrome.browser.vr.WebXrVrInputTest#testPresentationLocksFocus__ChromeTabbedActivity
org.chromium.chrome.browser.vr.WebXrVrInputTest#testPresentationLocksFocus_WebXr__CustomTabActivity
org.chromium.chrome.browser.vr.WebXrVrInputTest#testScreenTapsRegisteredOnCardboard__ChromeTabbedActivity
org.chromium.chrome.browser.vr.WebXrVrInputTest#testScreenTapsRegisteredOnCardboard_WebXr__WebappActivity
org.chromium.chrome.browser.vr.WebXrVrInputTest#testPresentationLocksFocus_WebXr__WebappActivity
org.chromium.chrome.browser.vr.WebXrVrTransitionTest#testNonImmersiveStopsDuringImmersive__WebappActivity

The failures are caused by these various assertions.

java.lang.AssertionError: Polling JavaScript boolean javascriptDone succeeded, but test failed. Testharness reported failure: "Harness failed due to timeout. FAIL Screen taps/clicks registered as input when in WebXR immersive session: null. "

java.lang.AssertionError: Polling JavaScript boolean javascriptDone succeeded, but test failed. Testharness reported failure: "Harness failed due to timeout. FAIL Focus is locked to presentation: null. "

java.lang.AssertionError: Polling JavaScript boolean javascriptDone succeeded, but test failed. Testharness reported failure: "Harness failed due to timeout. FAIL Screen taps/clicks registered when in VR: Test timed out. 

"java.lang.AssertionError: Polling JavaScript boolean javascriptDone succeeded, but test failed. Testharness reported failure: "Harness failed due to timeout. FAIL Focus is locked to immersive session: null. "

I'm guessing this could be a flakiness/the device is in a weird state?

Comment 1 by cjgrant@chromium.org, Sep 7

Owner: bsheedy@chromium.org
Status: Assigned (was: Untriaged)
Brian, could you take a look and reassign or mark Available as necessary?

Comment 2 by bsheedy@chromium.org, Sep 7

Status: Started (was: Assigned)
Looking into this. There shouldn't be anything special about the 64 bit tester that would be causing failures like this, so my initial guess is that some of the devices are going bad, but not sure at the moment.

Comment 3 by bsheedy@chromium.org, Sep 7

Cc: bpastene@chromium.org
Out of the last 200 runs, the VR instrumentation tests have been reported as failing five times. Three of those were due to an infra error where no devices were found and not due to the tests themselves, e.g. https://chromium-swarm.appspot.com/task?id=3f99294db138fe10&refresh=10&show_raw=1.

One of the two actual failed runs was due to a single test failing (WebXrVrInputTest#testScreenTapsRegisteredOnCardboard) that has no sign of flakiness before or after that particular failure. The device it ran on has been quarantined, which may be related https://chromium-swarm.appspot.com/bot?id=build420-m1--device3&sort_stats=total%3Adesc.

The final (and most recent) failed run had a bunch of failed tests, but again, no signs of flakiness before or after that. The device it ran on is still up https://chromium-swarm.appspot.com/bot?id=build437-m1--device5&sort_stats=total%3Adesc and has been consistently getting a few failures, but it doesn't look particularly unhealthy.

Ben, any thoughts on whether that last device is dying? It's not as dramatic as when a few of the K bots went bad, but I'm not sure what's an acceptable level of failed tests.

Comment 4 by bsheedy@chromium.org, Sep 12

Status: WontFix (was: Started)
I haven't seen any more VR-related flakes on the bot, so I think it's safe to say it was a one-time or device-related issue. Feel free to re-open if it pops up again.
►

Sign in to add a comment