New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 871763 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 863049



Sign in to add a comment

Viz failing VR tests on android-kitkat-arm-rel

Project Member Reported by jonr...@chromium.org, Aug 7

Issue description

OS: Android
Bot: android-kitkat-arm-rel
Test suite: chrome_public_test_vr_apk
Test: Several such as 
org.chromium.chrome.browser.vr.WebXrVrTransitionTest#testWindowRafStopsFiringWhilePresenting_WebXr__ChromeTabbedActivity

Failing Run: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-kitkat-arm-rel/49943

Some Failures:
   Polling JavaScript boolean javascript Done 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. "
       - "Harness failed due to timeout. FAIL Non-immersive rAF stops during immersive session: null. "
       - "Harness failed due to timeout. FAIL Focus is locked to immersive session: null. " 
   java.lang.AssertionError: Immersive session started, but browser not visibly in VR


 
Blockedon: 863049
Likely a side effect of GL OOM error we are seeing on teardown. See  issue 863049 
Status: WontFix (was: Untriaged)
The GL fix seems to have cleared this up

Sign in to add a comment