New issue
Advanced search Search tips

Issue 710534 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-XR

Blocking:
issue 709620



Sign in to add a comment

Investigate intermittent VR swarming test failure

Project Member Reported by bsheedy@chromium.org, Apr 11 2017

Issue description

WebVR's testScreenTapsRegisteredOnCardboard test is failing 1-2 times a day on the N5 w/ L swarming bots due to timing out waiting for a JavaScript step to finish (see https://build.chromium.org/p/chromium.fyi/builders/Android%20VR%20Tests/builds/6533).

Have not yet been able to reproduce locally using a N5 with the same Android version flashed on it. However, the most likely failure place is where it waits for the screen tap while in VR.

Marked as blocking the addition of the tests to the main waterfall since we don't want yet another test failing there.
 
This is looking like some device issue. I haven't been able to reproduce locally, and it seems to have stopped failing on the swarming bots, including the dozens of times I manually triggered the tests on the bot they've failed on.

Additionally, the logs of failed tests show an absurd number of the following line:
Adreno-ES20: <rb_adjust_internal_multisample_count:3892>: Reducing MSAA sample count from 4 to 2

as well as some thermal warnings, with the temperature gradually increasing:
ThermalEngine: TM Id 'SKIN_THERMAL_management_1' Sensor 'xo_therm_pu2' - alarm raised 2 at 42.0 degC

The test seems to have been failing due to the screen taps not actually getting sent, which caused the test to time out:
InputManager: Input event injection from pid 31521 timed out.
Status: WontFix (was: Started)
Closing for now since this seems to have resolved itself though the magic of swarming. Will re-open if it pops up again.
Components: Blink>WebXR

Sign in to add a comment