Philip Jägenstedt

It was pretty easy to find a timeout in the latest run as well, one that wasn't a timeout in the run before: https://wpt.fyi/generic-sensor/idlharness.https.html?sha=03d67ae5d9 https://wpt.fyi/generic-sensor/idlharness.https.html?sha=7a4c0d6617 So I think the issue...

https://wpt.fyi/webrtc/historical.html is another case that I wanted to look at just now and noticed it's timeout. Also a regression from the previous run: https://wpt.fyi/webrtc/historical.html?sha=03d67ae5d9 https://wpt.fyi/webrtc/historical.html?sha=7a4c0d6617

@jugglinmike what is the status of this? We could have this be entirely a matter for the results receiver (https://github.com/web-platform-tests/wpt.fyi/issues/55) to validate, but perhaps you still want to have some...

@jugglinmike this is done now, right?

I think there's still some problem here. This test passes in content_shell and opening the test and ref in a vanilla Chrome they *look* the same. Firefox too. Would need...

Another category of cleanup is bugs that are closed but the failures remain. Those need re-triage.

@KyleJu do you have any thoughts about how this could be implemented?

I keep removing closed bugs manually with PRs like these: - https://github.com/web-platform-tests/wpt-metadata/pull/3260 - https://github.com/web-platform-tests/wpt-metadata/pull/3806 - https://github.com/web-platform-tests/wpt-metadata/pull/4077 - https://github.com/web-platform-tests/wpt-metadata/pull/4122 - https://github.com/web-platform-tests/wpt-metadata/pull/4779 - https://github.com/web-platform-tests/wpt-metadata/pull/4785 - https://github.com/web-platform-tests/wpt-metadata/pull/4791 - https://github.com/web-platform-tests/wpt-metadata/pull/4874 - https://github.com/web-platform-tests/wpt-metadata/pull/4916 - https://github.com/web-platform-tests/wpt-metadata/pull/4943...

@stephenmcgruer

Around the same time I filed this issue I also wrote a script in https://github.com/web-platform-tests/wpt-metadata/tree/bug-list cc @KyleJu