-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
Intermittent buildbot failure and timeout on Android aarch64 #124666
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
Comments
It's happened 3 more times in the last week, both on the main and 3.13 branches:
It's only been seen on aarch64, but this probably isn't because of an architecture difference, but because the aarch64 runner is significantly faster than the AMD64 one. The reported failure varies between test_bytes or test_str. I still don't know why it's failing, but my guess is that the |
Ensures that failures in test setup don't result in dangling threads.
) Ensures that failures in test setup don't result in dangling threads. (cherry picked from commit 01b5abb) Co-authored-by: Malcolm Smith <[email protected]>
…131433) Ensures that failures in test setup don't result in dangling threads. (cherry picked from commit 01b5abb) Co-authored-by: Malcolm Smith <[email protected]>
Ensures that failures in test setup don't result in dangling threads.
Ensures that failures in test setup don't result in dangling threads.
Bug report
Happened twice in the last two days:
In both cases, the sequence of events is:
TestAndroidOutput.test_bytes
fails due to not finding the test start marker line in the logcat. A "threading._dangling was modified" warning is also shown.Linked PRs
The text was updated successfully, but these errors were encountered: