-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Description
I've seen several PRs in the past few weeks where the "Google testing" check starts, then stays in "Pending" status indefinitely, for a day or more.
A recent example is #122225. After updating the PR Monday morning, the check stayed pending all day. After a bit over 24 hours I updated the PR again to restart the check; it's still pending now, another 24 hours after that.
In the case of that PR, I asked in #hackers-infra and learned that the second check (at least) did run, and reported some results internally; the status just never made it back to GitHub. (I'm not sure whether the tests ran all the way to completion.)
The workaround I know of is to update the PR so that the check starts again. As in the case of #122225, this doesn't always work; the retry might get stuck too. In any case, because "Google testing" results can take up to 2 hours even when all's well, this adds at least 2 hours of turnaround time for each retry.
Possible related issues:
- frob can be missing the status too: https://github.com/flutter/flutter/pull/119495 google testing is missing #119767
- While the status is pending, the autosubmit bot doesn't wait for it: autosubmit bot submits without waiting for green Google Testing #122543
- The check is "flaky" but I'm not sure what that means (presumably the Google-internal bug says more): Google Testing CI check is flaky #116357