-
-
Notifications
You must be signed in to change notification settings - Fork 695
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
Testbed failure in test_window_state_rapid_assignment #3016
Comments
I am looking into this and will report back soon. |
Now a different but related test has failed on macOS x86_64: |
I couldn't reproduce this on my machine locally. On the CI also, I couldn't reproduce it: https://github.com/proneon267/toga/actions/runs/12190500356/job/34007856201. Could you re-run the failed job to make sure that the failure wasn't random? Also, the test passes successfully on the CI from another PR: https://github.com/beeware/toga/actions/runs/12190718820/job/34008472836 If the tests still fail then the solution would be to do the window state cleanup at the end of the test itself, instead of relying on window_cleanup to reset the window state. I'll try this once we confirm that the failure still exists. |
It's definitely an intermittent failure; being hard to reproduce doesn't mean it doesn't exist, though. I've done a bunch of rebuilds on the pass that failed, and there's been a couple of other CI passes since then, and I haven't seen another failure. It's also interesting to note that although the general failure mode is similar, the failure was on the slow test, not the rapid one. This suggests to me that the issue might have been a momentary slowdown on the machine (paging something out of cache, or something), so the GUI didn't respond inside the expected time window. In the process of investigating the "rapid" fix, it occurred to me that especially for these resize operations, we might be better served implementing |
I agree, polling based waiting seems to be the ideal solution to these types of intermittent failures. I'll research more about it and report back. |
Here's another CI failure, this time on Linux Wayland:
|
This test was merged 2 days ago from #2473 by @proneon267.
It's failing intermittently on GitHub Actions:
But it's 100% reproducible locally for me:
When the test runs, I get an error sound effect, the same one as if you press Cmd-C in the TextEdit app with nothing selected.
The text was updated successfully, but these errors were encountered: