@XilaiZhang Could you help take a look?

https://github.com/flutter/flutter/wiki/Understanding-Google-Testing#my-cl-reached-max-number-of-retry-why-and-how-do-i-resolve-this

This is concerning as the only solution offered is to ask a Googler to investigate or follow the solutions below:

1. rebase and ignore google testing which it looks like you cannot or
2. wait for commits to catch up and hope the conflict is resolved then resubmit or
3. manually override if you are a Googler, which you can no longer do.

Can we revert this functionality at this time?

Some more examples of this:
#134629
#134628
#134607
#134596
#134590

Marking as P1 considering high impact but there is a workaround to reset the test status considering this is a false alarm.

sent cl/565087659 for review and put more context in #134637 (comment)

I have a couple PRs (#134493, #134542) that are having this issue to. Will overriding the status even work if FroB says it's "Deleted" and there's no CL?

yes it would work even if its deleted and theres no cl

I tried overriding the Google testing status in FroB and it worked temporarily (said it was passing in the Github checks), but when it tried to autosubmit, it failed with message

auto label is removed for flutter/flutter/134493, due to - The status or check suite [Google testing](https://github.com/flutter/flutter/wiki/Understanding-Google-Testing#my-cl-reached-max-number-of-retry-why-and-how-do-i-resolve-this) has failed. Please fix the issues identified (or deflake) before re-applying this label.

#134493

umm i tried the same with autosubmit but for some reasons autosubmit merged it. Would be great if you could file a bug and document what happened. thank you!

Latency in reporting the status?

Latency in reporting the status?

It went from red -> green -> red again? and persisted red, until Xilai overrode it a second time from FRoB.

Latency in reporting the status?

It went from red -> green -> red again? and persisted red, until Xilai overrode it a second time from FRoB.

I did not know that.

This happened again on #134590 cc @XilaiZhang

I will file a separate issue for the check going from green back to red: #134684 public, with cross-link to Google-internal bug.

Isn't that part of this issue? Also what is the work around here then? Do you need to go on Frob and toggle the status to land the PR? I am assuming you do not since you can squash and merge in flutter.

Isn't that part of this issue? Also what is the work around here then?

If you're referring to #134684, it is not obvious to me that it is the same issue as this one. I will defer to you however if you think it is the same issue.

@christopherfujino no I am fine with this, I thought the actual issue was the one you pointed out. My mistake I thought there were two issues beyond the missing triage info. Please keep it open.

Hi @XilaiZhang, any updates on this? Just caught up on the thread

Yeah i sent updates in the PSA on Saturday

Gotcha. Thanks! I will close this, but feel free to reopen if necessary.

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.