Philip Jägenstedt

Flakiness isn't what I wanted to discover, what I have in mind is a change to testharness.js or something in tools/ breaking a lot of tests. In other words, we'd...

Well, dealing with flakiness might be a blocker to make this useful, but there's still wpt.fyi work: - see if there are regressions outside of the affected tests (or just...

Travis and Azure Pipelines can notify failures by email, maybe something like that could work? @lukebjerring you had some idea about notifications for other purposes already I think?

Right, I know that the checks exist, but you have to go looking for them.

@fantasai @frivoal @plinss @tabatkins

This was incredible painful when filing https://github.com/web-platform-tests/wpt/issues/32925. We have a "show history" button on wpt.fyi, but it doesn't really work. I ended up having to tweak a command line script...

That's pretty nice! And it only makes 29 requests, unlike wpt.fyi which has to make hundreds of requests, basically one per red/green square. That's because we don't have the data...

I was thinking about what the storage here has to look like. One way to represent all of our results would be in a giant denormalized database with many billions...

It sounds like something we might have discussion, yeah. This would be the code to change right? https://github.com/web-platform-tests/wpt.fyi/blob/b13ac69e72416b99e98583da5eaf4c8941af09ac/webapp/components/compat-2021.js#L485-L496

I've invoked `curl -f -s -S -d "artifact=safari-preview-affected-tests" -X POST https://wpt.fyi/api/checks/azure/25580` again manually just now, with success. So the problem was a transient one, where a retry would probably have...