Philip Jägenstedt

Thanks for investigating Mike! Do you think it'd be worth trying more aggressive restarting, and perhaps more chunks, to mitigate breakage like this?

Oh, if it's already 100 chunks, then scratch that idea. Seems like something is broken with Sauce or the sauce support in `./wpt run` then?

Still no results on wpt.fyi, what is the status of the Edge run that started after the fix?

71fe0a6c3d was the daily commit, and Taskcluster got started for it: https://tools.taskcluster.net/groups/FJTQgT1GQ1qVCsAwYXVKzg But it failed, I've filed https://github.com/web-platform-tests/wpt/issues/13989.

I'm included to say that rather than disabling the requirement, tests should be adapted to pass the requirement. A bit of work, though, for sure.

I mean tests using the existing `test_driver.click` to satisfy the requirement, i.e. the last option, "the test does not rely on autoplay and instead uses WPT's testdriver tool to trigger...

@mounirlamouri, I can't find where `--autoplay-policy=no-user-gesture-required` is passed when running LayoutTests, but I do see `--autoplay-policy=document-user-activation-required` for the virtual test suite you mentioned, so presumably something other than that is...

OK, looks like `--autoplay-policy=no-user-gesture-required` actually is still the default code-wise, to be flipped after a successful autoplay launch? Details aren't important for this issue, the question is only whether we...

@jugglinmike do you have logs available for these runs, to see if they provide any clues?

`--channel=preview` should also work after https://github.com/web-platform-tests/wpt/pull/13460 too.