[issue35620] asyncio test failure on appveyor

Change by Andrew Svetlov : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue35620] asyncio test failure on appveyor

Karthikeyan Singaravelan added the comment: asyncio tests are stable now and I couldn't find related reports. I guess it's fixed in one of the commits and also AppVeyor is not used anymore. I guess this can be closed as outdated. -- nosy: +xtreak

[issue35620] asyncio test failure on appveyor

Terry J. Reedy added the comment: My position is that tests that are known to occasionally fail independently of any changes in particular PRs should not be allowed to block merging. In the context of CI, the failure is a lie. One solution, and the easiest, is to disable the test. That is

[issue35620] asyncio test failure on appveyor

Andrew Svetlov added the comment: Do you mean an environment modification? 1 test altered the execution environment: test_asyncio -- ___ Python tracker ___

[issue35620] asyncio test failure on appveyor

New submission from Terry J. Reedy : https://ci.appveyor.com/project/python/cpython/builds/21296354?fullLog=true Blocked merge. Passed on Azure Pipeline +- same time. Appveyor re-run passed. Please disable or weaken the false positive tests. I will propose a different solution elsewhere,