cbuildbot --remote cannot detect videotest failure |
||||
Issue descriptionChromePFQ has build failure video_ChromeHWDecodeUsed failures. I tried bisecting using cbuildbot --remote tricky-tot-chrome-pfq-informational --chrome_version=[xxx] The lower bound chromium revision of bad build still passes. Local device test also shows the test failure. So, there are something different betwen chrome-pfq builds and cbuildbot. Yesterday, we got some time wasted on waiting for the results from cbuildbot. Link to the fact: https://bugs.chromium.org/p/chromium/issues/detail?id=674209#c12
,
Jan 25 2017
if non-official builds on cbuildbot, they should fail on all h264 videotests. My guess is they just skipped videotests as the log is very very sparse: https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/chrome_pfq_informational/builds/29/steps/HWTest%20%5Bbvt-cq%5D/logs/stdio
,
Jan 26 2017
Yes, it didn't run anything on hardware. Only VMTest. I find it difficult to convince tryjobs to use actual hardware, at least in one pass. It would be very nice if it did though.
,
Feb 1 2017
,
Feb 9 2017
Did you use the --hwtest flag? If not, this skip is expected
,
Feb 10 2017
I didn't. So this could be a Wontfix and be updated in YAQS?
,
Feb 16 2017
Verified in a recent run with --hwtest |
||||
►
Sign in to add a comment |
||||
Comment 1 by jamescook@chromium.org
, Jan 25 2017