Seems to be a one-time occurence. Will try to repro and see if I can find something in the logs.

Same issue with Kevin on R65: http://ubercautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/204779462-chromeos-test/chromeos6-row1-rack24-host21

Any update on this? (CrOS Media Sheriff ping)

Same issue also on poppy: https://stainless.corp.google.com/browse/chromeos-autotest-results/219880101-chromeos-test/chromeos2-row6-rack3-host9/

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

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

commit 390008e8b3c80c03f92afe0bd7d9b76e252b8823
Author: Alexandre Courbot <acourbot@chromium.org>
Date: Tue Oct 02 16:17:30 2018

video_VideoSeek: improve timeout detection

The timeout detection simply consisted in triggering a timeout error if
the test took more than 180 seconds to complete. This can become a short
time to do 100 seeks, especially if the network conditions are not
optimal - as a result, many lab boards were reporting a timeout after
~70 iterations.

Fix this by doing the timeout check not on the whole test, but for each
individual seek: we consider a timeout has occured if we stay more than
60 seconds on the same seek.

BUG= chromium:822582 
BUG=chromium:835679
BUG= chromium:846239 
BUG= chromium:856171 
BUG=chromium:884583
BUG=b:62360942
TEST=Checked that the test completed succesfully on Eve.

Change-Id: I1d53a7a314b4a20e9f2be506a1bdf8e42de0c266
Reviewed-on: https://chromium-review.googlesource.com/1256582
Commit-Ready: Alexandre Courbot <acourbot@chromium.org>
Tested-by: Alexandre Courbot <acourbot@chromium.org>
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>

[modify] https://crrev.com/390008e8b3c80c03f92afe0bd7d9b76e252b8823/client/site_tests/video_VideoSeek/video_VideoSeek.py

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

commit 05874e747ce606225a1884763c23b119a2fa0dec
Author: Alexandre Courbot <acourbot@chromium.org>
Date: Fri Oct 05 04:39:23 2018

video_VideoSeek: improve timeout detection

The timeout detection simply consisted in triggering a timeout error if
the test took more than 180 seconds to complete. This can become a short
time to do 100 seeks, especially if the network conditions are not
optimal - as a result, many lab boards were reporting a timeout after
~70 iterations.

Fix this by doing the timeout check not on the whole test, but for each
individual seek: we consider a timeout has occured if we stay more than
60 seconds on the same seek.

BUG= chromium:822582 
BUG=chromium:835679
BUG= chromium:846239 
BUG= chromium:856171 
BUG=chromium:884583
BUG=b:62360942
TEST=Checked that the test completed succesfully on Eve.

Change-Id: I1d53a7a314b4a20e9f2be506a1bdf8e42de0c266
Reviewed-on: https://chromium-review.googlesource.com/1256582
Commit-Ready: Alexandre Courbot <acourbot@chromium.org>
Tested-by: Alexandre Courbot <acourbot@chromium.org>
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
(cherry picked from commit 390008e8b3c80c03f92afe0bd7d9b76e252b8823)
Reviewed-on: https://chromium-review.googlesource.com/c/1264115
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>

[modify] https://crrev.com/05874e747ce606225a1884763c23b119a2fa0dec/client/site_tests/video_VideoSeek/video_VideoSeek.py

This should be fixed now.

Verified using https://stainless.corp.google.com/search?view=matrix&row=model&col=build&first_date=2018-10-03&last_date=2018-10-09&test=video_VideoSeek&build=R71-11140.0.0&board=falco&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false