kevin/reef: [flaky] video_ChromeVidResChangeHWDecode.h264 Error: Video did not signal ready in time. |
||
Issue descriptionRecently observed flakiness of video_ChromeVidResChangeHWDecode.h264 https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/testDetails?milestone=69&daysBack=30&testName=video_ChromeVidResChangeHWDecode.h264 kevin 10883.0.0 https://stainless.corp.google.com/browse/chromeos-autotest-results/217903417-chromeos-test/chromeos6-row2-rack24-host7/ kevin 10880.0.0 https://stainless.corp.google.com/browse/chromeos-autotest-results/217598899-chromeos-test/chromeos6-row2-rack24-host7/ reef 10883.0.0 https://stainless.corp.google.com/browse/chromeos-autotest-results/217867696-chromeos-test/chromeos6-row4-rack9-host18/ 07/16 18:24:57.427 DEBUG| method_logger:0026| + NativeHtml5Player.wait_for_video_ready 07/16 18:24:57.428 DEBUG| method_logger:0026| + NativeHtml5Player._wait_for_event 07/16 18:24:57.429 DEBUG| method_logger:0032| *** Begin arguments: 07/16 18:24:57.430 DEBUG| method_logger:0033| (<bound method NativeHtml5Player.is_video_ready of <autotest_lib.client.cros.video.native_html5_player.NativeHtml5Player object at 0xe8e77170>>, 'Video did not signal ready in time.') 07/16 18:24:57.431 DEBUG| method_logger:0034| === End arguments.
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||
►
Sign in to add a comment |
||
Comment 1 by jcliang@chromium.org
, Jul 23