| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
!buildbot android |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @mhsmith for commit 4997d1b 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F131427%2Fmerge The command will test the builders whose names match following regular expression: android The builders matched are:
|
Sorry, something went wrong.
There was a problem hiding this comment.
Seems like a reasonable set of fixes to me. If nothing else, I guess this means the failure case will actually fail, rather than timing out, which is a definite improvement; maybe the new failure will reveal more detail about why it's failing? (We can but hope :-) )
Sorry, something went wrong.
|
Thanks @mhsmith for the PR, and @freakboy3742 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
) Ensures that failures in test setup don't result in dangling threads. (cherry picked from commit 01b5abb) Co-authored-by: Malcolm Smith <smith@chaquo.com>
|
GH-131433 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
Ensures that failures in test setup don't result in dangling threads.
| Back | FazBrowse Home | New Git URL |
The hanging buildbot in #124666 was caused by a leftover thread created in the test's setUp method. It was supposed to be cleaned up by tearDown, but that isn't called automatically when setUp fails.
I still don't know why the underlying test failure was happening, but I've increased all the timeouts to LOOPBACK_TIMEOUT (10 seconds) in case that makes a difference.
Also cleaned up a couple of other test failure logging issues.