The following build appears to have some sort of DUT / graphics related failure, but it is difficult to triage:

https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/1310


From the stdio, there are several failures with:

video_ChromeHWDecodeUsed.vp9.mse        TEST_NA: Test skipped, no DUTs with expected labels found

I suspect this is because the DUT rebooted? We may want to improve that messaging.


Then we have:

video_VideoSanity.h264                  ABORT: Timed out, did not run.
and
graphics_dEQP                           TEST_NA: No test cases found for filter: dEQP-GLES31.info!

I suspect one of those may have been the cause of the reboot?

There are 5 test runs labeled "graphics_dEQP", this is very confusing.

I followed the one that matches the order of the failing test and found:
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/68224929-chromeos-test/chromeos4-row2-rack3-host6/graphics_dEQP/debug/

With:

07/01 11:07:40.190 DEBUG|        base_utils:0185| Running 'wflinfo -p null -a gles2'
07/01 11:07:40.271 ERROR|     setup_modules:0085| Exception occurred formatting message: 'Found gles%d.%d.' using args ((3, 0),)
...
07/01 11:07:40.523 ERROR|         traceback:0013| TypeError: %d format: a number is required, not tuple

Then:

  File "/usr/local/autotest/tests/graphics_dEQP/graphics_dEQP.py", line 543, in run_once
    self._filter)
TestNAError: No test cases found for filter: dEQP-GLES31.info!