This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author taleinat
Recipients taleinat, terry.reedy, vstinner
Date 2021-06-02.19:31:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
> Running 12 duplicate tests in parallel on Windows on a 6 core (12 CPU) machine with [...] resulted in nearly all failing.

Yes, running test_idle in parallel with itself usually causes some failures due to UI focus being stolen from one instance by another.  That's why I just ran this test rather than the whole test suite.

> I am reluctant to add a delay that is mostly not needed, so i tried the uploaded 'adaptive' code to only add a long delay if needed.  Uploaded.  But when a tested failed once, it failed again even with the delay, and contrary to the results above.

The delay needs to be placed carefully.  Changing root.after(1, ...) to use 50 rather than 1 (these are milliseconds) seems to resolve the issue entirely on my machine, at the cost of this single test taking 0.4 seconds to run rather than about 0.045 seconds.

> The other thing I thought is parameterizing the decorator to pass in a delay only for this test, but that require another layer of wrapping, which I cannot do right now.

I can do that.  Though I fear this may happen for other such tests as well...  Worth a shot I guess.
History
Date User Action Args
2021-06-02 19:31:55taleinatsetrecipients: + taleinat, terry.reedy, vstinner
2021-06-02 19:31:55taleinatsetmessageid: <[email protected]>
2021-06-02 19:31:55taleinatlinkissue44282 messages
2021-06-02 19:31:55taleinatcreate