Looks like regression related resolution change happens from 11265.0.0. video_ChromeVidResChangeHWDecode https://stainless.corp.google.com/search?view=matrix&row=board&col=build&first_date=2018-11-13&last_date=2018-11-19&test=video_ChromeVidResChangeHWDecode&exclude_cts=false&exclude_not_run=false&exclude_non_release=false&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false video_VideoSeek.h264.switchres https://stainless.corp.google.com/search?view=matrix&row=board&col=build&first_date=2018-11-13&last_date=2018-11-19&test=video_VideoSeek.h264.switchres&exclude_cts=false&exclude_not_run=false&exclude_non_release=false&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false video_VideoSeek.vp8.switchres https://stainless.corp.google.com/search?view=matrix&row=board&col=build&first_date=2018-11-13&last_date=2018-11-19&test=video_VideoSeek.vp8.switchres&exclude_cts=false&exclude_not_run=false&exclude_non_release=false&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false
Bisect revealed that this was caused by https://chromium-review.googlesource.com/c/chromium/src/+/1328634. As it turns out, this CL has just been reverted by https://chromium-review.googlesource.com/c/chromium/src/+/1340378. So hopefully the failures should stop as soon as tomorrow. Aka, if you plan to reland this patch in the future, please make sure that video_VideoSeek.h264.switchres still passes on e.g. Eve. Closing as the problem seems to be solved.
Comment 1 by acourbot@chromium.org
, Nov 19Status: Fixed (was: Assigned)