https://stainless.corp.google.com/search?view=matrix&row=model&col=build&first_date=2018-02-09&last_date=2018-03-08&test=video_YouTubeHTML5&build=R65-*&exclude_cts=false&exclude_not_run=false&exclude_non_release=false&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true https://stainless.corp.google.com/search?view=matrix&row=model&col=build&first_date=2018-02-09&last_date=2018-03-08&test=video_YouTubeHTML5&build=R66-*&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true https://stainless.corp.google.com/search?view=matrix&row=model&col=build&first_date=2018-02-09&last_date=2018-03-08&test=video_YouTubeHTML5&build=R67-*&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true As the issue is seen on all milestones, it might impacting from server side changes.
I don't have access the the test result link. posciak@, can you triage this bug and assign appropriately?
avkodipelli@, do you still see this issue?
Yes, this issue is still observing on latest builds. https://stainless.corp.google.com/search?view=matrix&row=model&col=build&first_date=2018-03-27&last_date=2018-04-02&test=video_YouTubeHTML5&build=R67-*&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true
posciak@, can you please assign appropriately?
Assigning to myself since I'm quite sure this is a test issue. This test may need to be rethought since it's brittle to changes within YouTube's resolution algorithms.
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/16b74bef5599bc5cdaf305cde9fe3efde3ed973c commit 16b74bef5599bc5cdaf305cde9fe3efde3ed973c Author: Vinayak Suley <vsuley@google.com> Date: Fri Apr 13 22:47:49 2018 Fixing YouTubeHTML5 flakiness YouTube uses a sophisticated algorithm to decide the playback resolution and its Javascript API for resolution change is merely a suggestion mechanism. As a result, we often see that the resolution we asked for is not delivered. I have spoken with YouTube folks and this is by design. I am removing the code we had to test resolution changing. It still validates playback and player states. BUG= chromium:820136 TEST=Tested on chromeos4-row4-rack6-host1 modified: client/cros/video/youtube_helper.py modified: client/site_tests/video_YouTubeHTML5/control modified: client/site_tests/video_YouTubeHTML5/video_YouTubeHTML5.py Change-Id: Ie0f6b3de5e08d255ddf6d23ac5416ae39df18647 Reviewed-on: https://chromium-review.googlesource.com/1006475 Commit-Ready: Vinayak Suley <vsuley@chromium.org> Tested-by: Vinayak Suley <vsuley@chromium.org> Reviewed-by: Krishna Gavini <krishnargv@chromium.org> Reviewed-by: Vinayak Suley <vsuley@chromium.org> [modify] https://crrev.com/16b74bef5599bc5cdaf305cde9fe3efde3ed973c/client/cros/video/youtube_helper.py [modify] https://crrev.com/16b74bef5599bc5cdaf305cde9fe3efde3ed973c/client/site_tests/video_YouTubeHTML5/video_YouTubeHTML5.py [modify] https://crrev.com/16b74bef5599bc5cdaf305cde9fe3efde3ed973c/client/site_tests/video_YouTubeHTML5/control
Working on latest builds: https://stainless.corp.google.com/search?view=matrix&row=model&col=build&first_date=2018-06-12&last_date=2018-06-18&test=video_YouTubeHTML5&build=R69-*&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true https://stainless.corp.google.com/search?view=matrix&row=model&col=build&first_date=2018-06-12&last_date=2018-06-18&test=video_YouTubeHTML5&build=R68-*&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true
Comment 1 by yini...@chromium.org
, Mar 19 2018