-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Taskcluster status checks not finishing and blocking PRs #14165
Comments
@jugglinmike have you heard back from the Taskcluster folks about this problem? Do you have up-to-date stats about how many PRs are affected? |
The status will be "Expected — Waiting for status to be reported" when this occurs. |
After consulting with @jgraham on IRC I've made the check not required while this is being resolved, and will assign to James. |
No, but you can keep an eye on the bug I filed to get the latest.
Sure. To keep things organized, I've reported the new stats in the original issue. I've also posted the new failures on that Taskcluster ticket. |
Thanks @jugglinmike! |
@jgraham can you help us poke for progress on this? |
Ping @jgraham any updates on this? |
https://bugzilla.mozilla.org/show_bug.cgi?id=1507254 has been resolved now. @jugglinmike can you get stats for the past week, to see if we can make stability blocking again? |
To give us a little more confidence, I'll verify all commits over the past 2 weeks (the bug was reported as "fixed" on 2018-11-28):
Good news! In that period, Taskcluster has reported results for every commit that TravisCI has reported results. All results
(For anyone interested in reproducing this data, the script I'm using is available here.) |
Excellent! I've made Taskcluster a required check for master again and so closing this issue. |
In #14088 (comment) @qiuzhong reported that Taskcluster isn't finishing and that they have seen this often recently. I made Taskcluster required just after I merged #14096, so that's why this has been happening only recently.
In #13194 (comment) we wondered what would happen, and now we know.
The text was updated successfully, but these errors were encountered: