| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. |
Sorry, something went wrong.
|
Sorry @zooba, I had trouble checking out the 3.11 backport branch. |
Sorry, something went wrong.
|
Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Sorry, something went wrong.
|
GH-100951 is a backport of this pull request to the 3.10 branch. |
Sorry, something went wrong.
|
GH-100952 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
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. (cherry picked from commit 5ff029f) Co-authored-by: Steve Dower <steve.dower@python.org>
| Back | FazBrowse Home | New Git URL |
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.