-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
A bunch of CI failures on main
branch
#97983
Comments
That's strange to have file access race emerged:
However, I'll create a reverting PR to stabilize the main and make the second attempt with all but asyncio tests manually disabled. |
@arhadthedev the same error message is seen in #97641 🤔 |
…_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 #97940 (comment). * Revert "gh-93357: Port test cases to IsolatedAsyncioTestCase, part 2 (#97896)" This reverts commit 09aea94. * Revert "gh-93357: Start porting asyncio server test cases to IsolatedAsyncioTestCase (#93369)" This reverts commit ce8fc18.
Merged, first thing in the morning. :-) Thanks for taking this seriously! |
For these failures, see issue #93919: On Windows, test_distutils and test_peg_generator leak a temporary file: Microsoft. |
…o.test_streams: port server cases to IsolatedAsyncioTestCase" (python#98015) This PR reverts pythongh-93369 and pythongh-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: pythongh-93357. First reported in python#97940 (comment). * Revert "pythongh-93357: Port test cases to IsolatedAsyncioTestCase, part 2 (python#97896)" This reverts commit 09aea94. * Revert "pythongh-93357: Start porting asyncio server test cases to IsolatedAsyncioTestCase (python#93369)" This reverts commit ce8fc18.
I created issue #98219 for "PermissionError: [WinError 32] The process cannot access the file because it is being used by another process". |
Thanks for filing this! Looks like all three issues have been taken care of |
The CI does not look good. There are multiple failures, they are unrelated, but all do happen on random commits.
Grouping them in one meta issue for now.
asyncio
failures:CI link: https://github.com/python/cpython/actions/runs/3193117202/jobs/5211355431#step:7:3155
Commit: b44372e
CI link: https://github.com/python/cpython/actions/runs/3193117202/jobs/5211355655#step:6:2850
Commit: b44372e
CI link: https://buildbot.python.org/all/#/builders/725/builds/2739
Commit: 23e83a8
The text was updated successfully, but these errors were encountered: