For the past week or so, we've been getting some flakes on the WebXrVrTransitionTest#testRequestPresentEntersVr and WebXrVrTransitionTest#testRequestSessionEntersVr instrumentation tests. These are always resolved by the automatic retries, but looking at the affected tasks, it's always on build36-b4--device2, so it looks like there's something off with that particular device.

The failure is caused by the test reaching the end, but detecting that the JavaScript testharness timed out (which takes 10 seconds). This only happens on those two tests, so it's likely related to the very rudimentary pixel tests they do https://cs.chromium.org/chromium/src/chrome/android/javatests/src/org/chromium/chrome/browser/vr/WebXrVrTransitionTest.java?q=webxrvrtransitiontest&sq=package:chromium&dr=CSs&l=130.

Either it's taking a really long time to get a screenshot, it's failing to get screenshots for a while, or the center of the eye isn't pure blue for a while (the post failure screenshot has it being pure blue, though). I added some logging and reproed on the device, but the logcat output is extremely unhelpful https://isolateserver.appspot.com/browse?namespace=default-gzip&digest=d5def40ba7c29a38624d22bbf6d05776a769436e&as=logcat.txt.

Probably best to just reflash it and see if the issue gets resolved?