Missing wpt.fyi checks

[foolip]

In web-platform-tests/wpt#18722 the Chrome and Firefox wpt.fyi checks weren't created, either for staging or prod.

Taskcluster as a whole did pass, so it's not because of stability checks failing which I first suspected.

[lukebjerring]

@foolip - this is actually working as intended; Taskcluster's use of wpt job ignores any changes to the resources/ directory.

web-platform-tests/wpt#18500 is the "fix", just waiting on review - it is distinguishing the stability check vs single-run cases, and letting idlharness.js trigger a single run.

[foolip]

Oh, so the reason we got Safari results is because we unconditionally run affected tests. (I did that to have results as fast as possible and most PRs do affect tests.)

[stephenmcgruer]

So the only remaining work here would be (if its not already happened) to make Safari runs not run unconditionally? Is that something we want to pursue @foolip or is it time to close this as fixed by #18500 ?

[foolip]

@stephenmcgruer this was resolved the other way around, after web-platform-tests/wpt#18500 touching idlharness.js runs all of the idlharness tests, and https://github.com/web-platform-tests/wpt/pull/19611/checks shows it in action.