diff options
| author | Oleg Iarygin <oleg@arhadthedev.net> | 2022-10-07 14:14:28 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-07 14:14:28 (GMT) |
| commit | f99bb20cde258bfd8404448951f5454dc6279e98 (patch) | |
| tree | 79a5d4f202c85aa36892e7e24e805c72f658a002 /Python/pytime.c | |
| parent | 6592a62ec2939323b895c85780da7fd73a640da3 (diff) | |
| download | cpython-f99bb20cde258bfd8404448951f5454dc6279e98.zip cpython-f99bb20cde258bfd8404448951f5454dc6279e98.tar.gz cpython-f99bb20cde258bfd8404448951f5454dc6279e98.tar.bz2 | |
gh-97983: Revert "Lay the foundation for further work in asyncio.test_streams: port server cases to IsolatedAsyncioTestCase" (#98015)
This PR reverts gh-93369 and gh-97896 because they've made asyncio tests unstable. After these PRs were merged, random GitHub action jobs of random commits started to fail unrelated tests and test framework methods.
The reverting is necessary because such shrapnel failures are a symptom of some underlying bug that must be found and fixed first.
I had a hope that it's a server overload because we already have extremely rare disc access errors. However, one and a half day passed, and the failures continue to emerge both in PRs and commits.
Affected issue: gh-93357.
First reported in https://github.com/python/cpython/pull/97940#issuecomment-1270004134.
* Revert "gh-93357: Port test cases to IsolatedAsyncioTestCase, part 2 (#97896)"
This reverts commit 09aea94d291fed2f3e96558dcd6db04014c3e2fb.
* Revert "gh-93357: Start porting asyncio server test cases to IsolatedAsyncioTestCase (#93369)"
This reverts commit ce8fc186ac81bce1727bf4192205148daabf5c2e.
Diffstat (limited to 'Python/pytime.c')
0 files changed, 0 insertions, 0 deletions