-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
Skip py.exe launcher tests in full layout CI test #100948
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
Conversation
Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. |
Sorry @zooba, I had trouble checking out the |
Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
GH-100951 is a backport of this pull request to the 3.10 branch. |
GH-100952 is a backport of this pull request to the 3.11 branch. |
These tests become flaky when py.exe exists on the test machin 8000 e but isn't the one that was just built. They also don't provide any useful information for this scenario, so easiest to just skip them. (cherry picked from commit 5ff029f) Co-authored-by: Steve Dower <steve.dower@python.org>
These tests become flaky when py.exe exists on the test machine but isn't the one that was just built. They also don't provide any useful information for this scenario, so easiest to just skip them. (cherry picked from commit 5ff029f) Co-authored-by: Steve Dower <steve.dower@python.org>
These tests become flaky when py.exe exists on the test machine but isn't the one that was just built. They also don't provide any useful information for this scenario, so easiest to just skip them. (cherry picked from commit 5ff029f) Co-authored-by: Steve Dower <steve.dower@python.org>
These tests become flaky when py.exe exists on the test machine but isn't the one that was just built. They also don't provide any useful information for this scenario, so easiest to just skip them.