jugglinmike

For a month or more, we've known that the "Edge/Windows/Sauce Labs" browser configuration consistently fails to report complete results. Specifically, the browser would crash, the WPT CLI would not respond...

With commit 84486a4fbf98e936618e1ff5e6ce808c79bbf877, I re-introduced the "retry" heuristic that we initially implemented in the previous infrastructure. I'm hopeful that this will allow us to recover from intermittent errors that previously...

That pull request was reviewed by its author, and as per gh-55, [the script assigns the latest reviewer](https://github.com/web-platform-tests/wpt-pr-bot/blob/b6b7fd1efb22d63f5c94cc39e04cdbd74ac1a8ab/lib/metadata/choose-assignee.js#L10-L14). That review came hours after the pull request was opened, though. So...

It looks like we can run Node.js code there, so as much as I'd like to rewrite this tool, we don't necessarily have to. That said, there are some reasons...

@foolip We might want to abstract [the approach that we developed for wpt.live](https://github.com/web-platform-tests/wpt/pull/19838). WPT could define a "scheduled" GitHub Action that only simulated pull request events [using the generic `repository_dispatch`...

It makes me wonder if GitHub has considered offering this kind of functionality directly. Maybe if the Workflows defined in the project's default branch were given some special status, then...

The best answer I can give is "I hope so." There's no question that we ought to be following POLP, though, so I'd like to help this move forward. Here's...

@lukebjerring I think that's an good interpretation of the feature and its intended use. If there's a bug here, it's that the script is too eager, and its immediate response...

Thanks for the report! The only change in the referenced pull request is a file deletion. That's fairly unique, so it initially seemed like an edge case we weren't handling...

> That error was the reason for filing https://github.com/web-platform-tests/wpt/issues/13710 so possibly the guess (by @tobie) at the cause was incorrect. The string "THIS SHOULDN'T EVER HAPPEN" is logged in response...