bpo-42142: Try to fix timeouts in ttk tests#23474
bpo-42142: Try to fix timeouts in ttk tests#23474serhiy-storchaka merged 6 commits intopython:masterfrom
Conversation
Check whether the widget is already visible before waiting a <VisibilityNotify> event.
|
Also addresses bpo-42370 |
|
Putting repeated problematic test im a function is a great idea. Pipelines Windows tests failed consistently with "RuntimeError: Widget .!labeledscale is still not mapped". Presume same for GH Actions. Maybe revert to wait_visibility on Windows, where it apparently always worked? |
|
Actually, using
|
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
Instead of using wait_visibility() which waits event <VisibilityNotify> in dead loop use update() which should proceed all queued events. (cherry picked from commit 6cc2c41) Co-authored-by: Serhiy Storchaka <[email protected]>
|
GH-23565 is a backport of this pull request to the 3.9 branch. |
Instead of using wait_visibility() which waits event <VisibilityNotify> in dead loop use update() which should proceed all queued events. (cherry picked from commit 6cc2c41) Co-authored-by: Serhiy Storchaka <[email protected]>
|
GH-23566 is a backport of this pull request to the 3.8 branch. |
Instead of using wait_visibility() which waits event <VisibilityNotify> in dead loop use update() which should proceed all queued events. (cherry picked from commit 6cc2c41) Co-authored-by: Serhiy Storchaka <[email protected]>
Instead of using wait_visibility() which waits event <VisibilityNotify> in dead loop use update() which should proceed all queued events. (cherry picked from commit 6cc2c41) Co-authored-by: Serhiy Storchaka <[email protected]>
Instead of using wait_visibility() which waits event <VisibilityNotify> in dead loop use update() which should proceed all queued events.
Check whether the widget is already visible before waiting a
<VisibilityNotify>event.https://bugs.python.org/issue42142