These should be triggered from refs/heads/epochs/daily I believe; I suspect the decision task graph work broke this.

Hrm, I am somewhat confused. If we go back to November 26th, we can see a commit (5454021b) which ran a taskcluster push, where picking any individual task shows it has \"ref\":\"refs/heads/epochs/daily\".

But if we look at November 30th, we find that epochs was pushed to 5df56b25e1, but looking at that commits page and grabbing the Taskcluster push linked there, and looking at the ref there of some random task we get \"ref\": \"refs/heads/master\".

So Taskcluster didn't trigger for epochs? I'm looking at the new .taskcluster.yml atm, trying to understand how that might have happened (but could be red herring?)

I just pushed to triggers/chrome_stable to see what would happen. Monitoring https://github.com/web-platform-tests/wpt/commits/triggers/chrome_stable; I would expect to see a TC run happen for refs/heads/triggers/chrome_stable.

As far as I can tell, nothing happened. https://github.com/web-platform-tests/wpt/commits/triggers/chrome_stable shows a bunch of Azure Pipeline runs going (which I think are from the actual master commit), but the TaskCluster run that is listed is also old and appears to be for refs/head/master.

Pushing triggers/firefox_nightly to see.

Firefox nightly works?!

https://github.com/web-platform-tests/wpt/commits/triggers/firefox_nightly shows https://community-tc.services.mozilla.com/tasks/ZGai_M8ZSxa9T3k3AQJBRg which has a ref of refs/heads/triggers/firefox_nightly ...

This is interesting. If we look at the commit for 5df56b2, it has an error in a comment at 7:36pm EST November 30th. That is the same time as the action that pushed that sha to the epoch branches happened.

Again it happens again for 9c100c3, again matching the epoch action timestamp.

I managed to find a log of the events github has sent, by looking at the dispatched events for one of our webhooks (that only listens to pushes).

event.sender.login for the epoch push is github-actions[bot], and I'll bet my hat Taskcluster won't accept that as an email...

This was hopefully fixed by #20561, we will see from today's daily push to epochs.

Looks like it -- 28b0967 includes Safari, Firefox and Chrome.