Skip to content

Conversation

@miss-islington
Copy link
Contributor

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>
@zooba
Copy link
Member

zooba commented Jan 11, 2023

Not needed for 3.10 - the tests were added in 3.11

@miss-islington miss-islington deleted the backport-5ff029f-3.10 branch January 11, 2023 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants