Luke Bjerring

@foolip - the wpt.fyi custom check does compare each full master run to the most recent master run for the same product, and surfaces the regressions. It's noisy due to...

OK - Then this isn't a wpt.fyi issue. wpt.fyi does detect regressions, but it gets ignored because of the flaky tests being noisy. The remaining work lies in fixing the...

I'm confused. The custom checks run for the full test suite comparison, on master for all commits. Example: https://github.com/web-platform-tests/wpt/runs/51187555 https://github.com/web-platform-tests/wpt/commits/master Changing the title to reflect the change that you're asking...

I think the first phase here is to have a point-of-contact for the runs, or at least a issue-filing template?

This request is UI for a part of the lifecycle project for the results receiver, which will eventually include a validation step.

One thing that is worth mentioning is that for the purposes of attribution for metadata changes, we're creating a GitHub OAuth login flow (which bubbles down to a "User" concept)....

From https://github.com/web-platform-tests/results-collection/issues/123, @gsnedders said: > That relies on everyone implementing runners correctly. I think there's definitely an argument that it's the collection side that should handle it? There's an imbalance...

https://www.webcomponents.org/element/@polymer/iron-list/demo/demo/index.html From Google search, initially, the landing page is actually https://www.webcomponents.org/element/polymerelements/iron-list But the UI redirects it to the `@polymer` npm package. As a result, the (first) demo link doesn't work:...

This is blocking https://github.com/w3c/web-platform-tests/pull/9884

Currently https://wpt.fyi/latest/{platform}/[test path] redirects to JSON for the test run. This may change with https://github.com/w3c/wptdashboard/issues/161 and https://github.com/w3c/wptdashboard/issues/172 being resolved.