This was fixed in https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/653957.

It is still failing with 9/13 autotest run.
log link: https://00e9e64bac30ec2b62aa56dc0c4bdd6f1d0620897b2a0132c9-apidata.googleusercontent.com/download/storage/v1/b/chromeos-autotest-results/o/141603827-chromeos-test%2Fchromeos1-row4-rack5-host5%2Fvideo_WebRtcResolutionSwitching%2Fdebug%2Fvideo_WebRtcResolutionSwitching.DEBUG?qk=AD5uMEuVf5yjxHmvItzcIVUkN2woAkXCzn43-zION4P6U4hypQUHgZAO0nsMHl0n8Y__2H5PIwx3XUrsXkCKVrmB8PKSo-zDra2zrJyVtMefIkNYJvxDFw9493myT1zCiqHYRHwxrS5Vp-6ndcSSn2-vDFD8wyfiidgnojp8RZpOU_CDBFPE-5dp1Xu7C-Yt8X8Hu1GxbdYcp6UV2xCDEAwlteU-oeFA5qpDi5Ire9xAWz_jvWls2D9nrx4Yv0EIE6wf5u0mA0VLK7JsWYkxNkr2y3ZCqUbVAJ1qKYD2Ggyv8jmB9zuTGIEHHcBMwj26h67stIGUIUSzB-UDrWFTZYyFWkmt7lrsFP2y-mwzmiged0Ch40DlCXjSDac1vYh6LAV-MT5FMqG0TuA4d0tuaSqNeIQmsv3yyiJBNw1gi434BlvYkH2NDL95C7COQwOgFDnxloBtdXMo9kwEAL7FnvVKbBSaaXm4Mbd7Pj_chBPY4porC3iftfVNsVpP5zjVj_O60N3Yz4qqZ6BC8-Poktl2TrjsLyXzyFH-EcDJERqXnPAlDA9ew-7Cos5ZMWnMA4yNeQl53vYBHU6JUl4pPa1Jp2EDaGwm1B5Xz-1IROG2Cxe0IT6MjUYkNzIn9El_iF1bn73Cw5xQoEXC3WgJZFGq3l3jspBRuNUVlcIzFWZWbnt0hAE7wguo3O6rAcmC4jEy0arsb8t2j9r5yWvsbyNIKV4v1sTx0PWFjZrtdayJoFYFOPQctNlBLLwWOYq_OrmlZmxCoJR0RUTboTsY5wIz644XVmeORUMLCOXEmY5BXUE754MBnbBBGPos-MGPKlk58M2lbThA8D59ciPPxUM3TKl0_m0QawiUZ-5xpzw7tFibWLbDZXQVQ3DKpEMosbT0ryajvRJbkcKSRzNnRNtuGNN9S_5G5R9zfxlwH8AkaISi4qftuBvHyFE0BqJ7F-ADEoh_xO-s

09/13 08:39:34.771 DEBUG|              test:0395| after_iteration_hooks completed
09/13 08:39:34.772 WARNI|              test:0612| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 606, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 806, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 470, in execute
    dargs)
  File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 380, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/cros/video/helper_logger.py", line 82, in call
    return func(*args, **kwargs)
  File "/usr/local/autotest/tests/video_WebRtcResolutionSwitching/video_WebRtcResolutionSwitching.py", line 77, in run_once
    self.wait_test_completed(TIMEOUT)
  File "/usr/local/autotest/tests/video_WebRtcResolutionSwitching/video_WebRtcResolutionSwitching.py", line 68, in wait_test_completed
    desc='test reports itself as finished')
  File "/usr/local/autotest/common_lib/utils.py", line 2725, in poll_for_condition
    value = condition()
  File "/usr/local/autotest/tests/video_WebRtcResolutionSwitching/video_WebRtcResolutionSwitching.py", line 62, in _test_done
    raise error.TestFail('Video is broken')
TestFail: Video is broken
09/13 08:39:34.775 DEBUG|              test:0617| Running cleanup for test.
09/13 08:39:34.775 DEBUG|   logging_manager:0627| Logging subprocess finished
09/13 08:39:34.776 DEBUG|   logging_manager:0627| Logging subprocess finished

Looks like https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/653957 needs to be merged back to M62

Yes, merging to M62 would fix this. Or disabling the test for M62 if that is easier - I don't see any danger in disabling these brand new tests. I'm not familiar with the merge process, can someone point me to docs?

For merge requests, start with applying labels as I did. Complete instructions: 
https://sites.google.com/a/google.com/chromeos/for-team-members/chronos-download/pmo/merge-instructions-to-a-release-branch?pli=1


Once merge is approved by the TPMs, you can go ahead and request cherry pick from gerrit. Click More > Cherry Pick > Enter R62 in "Cherry Pick to branch" .. after this a new CL will be created if there are no merge conflicts or a message will appear if there are merge conflicts. In the case of merge conflicts, you will need to resolve those and try cherry pick again.

This bug requires manual review: M62 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

video_WebRtcResolutionSwitching fails for R62 for all platforms. 
https://wmatrix.googleplex.com/failures/unfiltered?suites=hotrod&tests=video_WebRtcResolutionSwitching&days_back=4&releases=62&hide_missing=True

Kerl@, is CL merged to 62?

No, it is not merged yet.

Merge approved for 62. 

I just tried the merge. It is quite painful and will require cherry-picking several commits. I don't see it being worth the effort - these tests are still under development and I am still working on de-flaking them, even on ToT.

I suggest we just ignore these failures (and all other failures from webrtc_PausePlayPeerConnections.video,webrtc_PausePlayPeerConnections.audio,video_WebRtcResolutionSwitching,video_WebRtcMainFeedSwitching) until I feel confident they are not too flaky.

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Removing merge label, instead of merging we have marked these tests as "under development" until they have stabilized.

 Issue 785107  has been merged into this issue.