-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing Chrome and Firefox stable wpt.fyi runs #20551
Comments
These should be triggered from |
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 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 So Taskcluster didn't trigger for epochs? I'm looking at the new |
I just pushed to |
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 |
Pushing |
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 |
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).
|
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. |
The latest wpt.fyi run that included Safari, Chrome and Firefox is 1df8c00.
Since then, there have been 20bb1ca, 5df56b2, and 9c100c3, all of which contain only Safari runs.
The text was updated successfully, but these errors were encountered: