| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
pythonGH-99859 introduced new buildbot failures, as reported [here](python#91054 (comment)). I was able to reproduce the failures with: ``` ./python.exe -m test -v test_capi.test_watchers -m "*TestCodeObjectWatchers*" -R 3:3 ``` The root cause appears to be to static events counters used in the tests, when running the tests with repetitions (using the same interpreter state), the counts from the first test run affected the next runs. This fixes it by resetting the counts when adding and clearing test watchers.
|
🤖 New build scheduled with the buildbot fleet by @AlexWaygood for commit 5a53c06 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Sorry, something went wrong.
|
Thanks a lot for the quick fix @itamaro! I will merge this if confirmed that this fixes the buildbots |
Sorry, something went wrong.
|
The two buildbot failures are unrelated and already exist on main: |
Sorry, something went wrong.
|
Merging this as this fixes most of the problems. Thanks a lot again @itamaro |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
GH-99859 introduced new buildbot failures, as reported here.
I was able to reproduce the failures with:
The root cause appears to be the static events counters used in the tests, when running the tests with repetitions (using the same interpreter state), the counts from the first test run affected the next runs.
This fixes it by resetting the counts when adding and clearing test watchers.