Output from issue 630825:

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/70569774-chromeos-test/chromeos2-row24-rack1-host17/graphics_Idle/debug/

07/22 22:53:31.441 WARNI|              test:0606| Autotest caught exception when running test:
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 804, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 461, in execute
    dargs)
  File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 376, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/graphics_Idle/graphics_Idle.py", line 52, in run_once
    raise error.TestFail(errors)
TestFail: Did not see the min i915 clock. 

Issue 628949 also has "Did not see the min i915 clock."
Issue 608782 is similar but with "did not see the GPU in RC6"

The symptom for issue 632268 was "Android did not boot", it is unrelated to the other failures.

issue 605125 has the symptom "Timed out going through login screen. OOBE not dismissed." Changing that to track issue 631640 instead.

Renaming this to reflect the symptoms of the three remaining blocking issues: "Did not see the clock/gpu"

The code for  "Did not see the min i915 clock" is here:

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/graphics_Idle/graphics_Idle.py?q=graphics_Idle.py&dr&l=177

And "did not see the GPU in RC6" is here:

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/graphics_Idle/graphics_Idle.py?q=graphics_Idle.py&dr&l=140

(both in graphics_Idle.py).

+marcheu@

These look to be pretty rare flake, ~ 2/month since May. We should keep an eye out for these symptoms, but they are pretty infrequent in the scheme of things. Lowering the priority.

The samus android pfq just failed twice in a row with this https://uberchromegw.corp.google.com/i/chromeos/builders/samus-android-pfq/builds/168

Do we have any leads on this?

Something is spinning CPU/GPU after login longer than usual when starting Android. I ran the test, but didn't see anything suspicious. This change basically is going to increase the wait:
https://chromium-review.googlesource.com/377627 

This test seems to work...