Hmm, there are two failures.
One seems a device issue; the device has kepler but avtest_label_detect doesn't detect.
chromeos2-row2-rack8-host5 may have something wrong.
"Dynamic capability detection results did not match static capability configuration. mismatch_list=['hw_dec_vp8_1080_30', 'hw_enc_vp8_1080_30']"

The other one is totally weird, managed-capabilities.yaml is not installed..
It should always put in the image. I think this is a kind of built system failure..

I have confirmed that that file does exist on moblab

chromeos2-row2-rack8-host5
total 16
-rw-r--r-- 1 root root  198 Nov  5 11:16 15-chipset-bdw-capabilities.yaml
-rw-r--r-- 1 root root   25 Nov  5 11:17 18-baseboard-jecht-capabilities.yaml
-rw-r--r-- 1 root root  160 Nov  5 11:17 20-guado-capabilities.yaml
-rw-r--r-- 1 root root 1269 Nov  5 11:15 managed-capabilities.yaml
+ ls -l /usr/local/etc/autotest-capability/

I can not find anything particularly wrong with chromeos2-row2-rack8-host5

I checked all the other moblab and I can see that file.  Moblab can be slower to boot up particular the first time after a provision so it might be a timing issue ?

Hi, haddowk@, sorry for delay response.
That would be reasonable.
Do you have any idea to resolve this timing issue?

Still happening (flaky 14%):
video_VideoCapability	guado_moblab	11429.0.0
http://ubercautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/268706769-chromeos-test/chromeos2-row2-rack8-host11

All GOOD in recent 28 days.