Fix potential flakiness in test_run_until_complete_baseexception - #100148
Conversation
Done & merged. |
|
This is indeed better than sleeping for a small delay. |
|
Yup, a very insightful solution. Thanks @fantix ! |
|
This PR appears to have resulted in an empty commit, likely because the PR branch was not fully up to date with |
Very weird. Especially since when I check out main and pull to head, the change is there, and attributed to this PR. So maybe the problem is with the GitHub UI? I saw some mention of enpty branches on Discord but chose to ignore it. |
|
Oh, weird. Yes, I see the same. It must be something wrong with the GitHub UI. My sincere apologies for the false accusation, @fantix! |
|
No worries @AlexWaygood , thank you for being careful ❤️ |
|
Hm, there's definitely something weird though. I see three commits for this PR in the main branch: Two of those are empty. What kind of GitHub hiccup could have caused that??? |

Refs #24477, use a more reliable way to run the test.
If the covering issue happens again, the loop would be requested to stop in the first iteration and got stopped after the first iteration. In that case, our
func()in the second iteration won't be called.