Look like this is caused by bad Chrome.

The log is from the code autotest here.
http://cs/chromeos_public/src/third_party/autotest/files/client/cros/video/histogram_verifier.py?l=43&rcl=584d243286f682dc1c2277873ce908b2503e55f6

Basically autotest want to open Chrome at chrome://histograms/Media.GpuVideoDecoderInitializeStatus but error occurs.

+hiroh

https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/740590

https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/734881

These look related but the timelines don't quite match.

RE 1 bad chrome would be my instinct too, but we haven't had a new chrome between the last 2 cq runs afaik.

I will fix this issue ASAP.

Shouldn't the test be disabled or the CL be reverted at this point? It's been two hours.

Agreed with #7. If we're not close to a fix, let's disable the tests to unblock CQ.

Preparing test-removal CL.

https://chromium-review.googlesource.com/#/c/chromiumos/third_party/autotest/+/757942 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/ac7554f1bc079cfe50212e788c5a5e7060606816

commit ac7554f1bc079cfe50212e788c5a5e7060606816
Author: Aviv Keshet <akeshet@chromium.org>
Date: Wed Nov 08 06:25:51 2017

temporarily move video tests out of CQ

BUG= chromium:782509 
TEST=None

Change-Id: I40c5fef86f192a3165141521788137746a5c0ffd
Reviewed-on: https://chromium-review.googlesource.com/757942
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Pawel Osciak <posciak@chromium.org>

[modify] https://crrev.com/ac7554f1bc079cfe50212e788c5a5e7060606816/client/site_tests/video_ChromeHWDecodeUsed/control.h264
[modify] https://crrev.com/ac7554f1bc079cfe50212e788c5a5e7060606816/client/site_tests/video_ChromeHWDecodeUsed/control.h264.mse
[modify] https://crrev.com/ac7554f1bc079cfe50212e788c5a5e7060606816/client/site_tests/video_ChromeHWDecodeUsed/control.vp8
[modify] https://crrev.com/ac7554f1bc079cfe50212e788c5a5e7060606816/client/site_tests/video_ChromeHWDecodeUsed/control.vp9
[modify] https://crrev.com/ac7554f1bc079cfe50212e788c5a5e7060606816/client/site_tests/video_ChromeHWDecodeUsed/control.vp9.mse
[modify] https://crrev.com/ac7554f1bc079cfe50212e788c5a5e7060606816/client/site_tests/video_ChromeHWDecodeUsed/control.vp8.mse

 Issue 782493  has been merged into this issue.

The root cause is crosvideo.appspot.com is gone.
The test try to use the video in the site.
vsuley@ is recently adding some changes in the site.

We can use crosvideo2.appspot.com instead as a temporal solution.
CL is here. crosreview.com/757890
I would move back these tests to CQ by the CL.

FYI: I filed an issue for fixing crosvideo.appspot.com server error.  crbug.com/782569 .
It should be a true solution for this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/78342815965c7524d994cfc245da0a99f684a34e

commit 78342815965c7524d994cfc245da0a99f684a34e
Author: Hirokazu Honda <hiroh@chromium.org>
Date: Wed Nov 08 16:28:36 2017

autotest: Fix video_ChromeHWDecodeUsed mse tests failure

video_ChromeHWDecodeUsed mse tests are failed because crosvideo.appspot.com is
broken down. We can temporarily use crosvideo2.appspot.com instead.

BUG= chromium:782509 
TEST=video_ChromeHWDecodeUsed on peach_pit

Change-Id: I0b6b6d400396529cf58b7ecddf52f9d3d4384e55
Reviewed-on: https://chromium-review.googlesource.com/757890
Commit-Ready: Hirokazu Honda <hiroh@chromium.org>
Tested-by: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>

[modify] https://crrev.com/78342815965c7524d994cfc245da0a99f684a34e/client/site_tests/video_ChromeHWDecodeUsed/control.h264
[modify] https://crrev.com/78342815965c7524d994cfc245da0a99f684a34e/client/site_tests/video_ChromeHWDecodeUsed/control.h264.mse
[modify] https://crrev.com/78342815965c7524d994cfc245da0a99f684a34e/client/site_tests/video_ChromeHWDecodeUsed/control.vp8
[modify] https://crrev.com/78342815965c7524d994cfc245da0a99f684a34e/client/site_tests/video_ChromeHWDecodeUsed/control.vp9
[modify] https://crrev.com/78342815965c7524d994cfc245da0a99f684a34e/client/site_tests/video_ChromeHWDecodeUsed/control.vp9.mse
[modify] https://crrev.com/78342815965c7524d994cfc245da0a99f684a34e/client/site_tests/video_ChromeHWDecodeUsed/control.vp8.mse

It seems a little worrisome for a test in the critical path to depend on an external service that can be turned down at any point. How do we prevent this from happening again in the future?

#16 should definitely be considered.
I will discuss with test team, if we can test video with MSE without Internet.
If it is impossible, should we move these mse tests to outside of CQ.

Discussed this with hiroh@, I think we can move the html/js assets to the code repository so that they are deployed along with the test so it can all be executed locally. We will try to use one of the videos already being deployed to DUTs to avoid increasing the size too much. 

Also, reducing priority since the bug is no longer blocking.

hiroh has created this issue to track the work suggested in #17. https://bugs.chromium.org/p/chromium/issues/detail?id=784742

This commit should take the tests back to crosvideo.appspot.com: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/18c6c70b2727ed93165e50964b7684e60db4fc89

Closing the bug as fixed.