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
Timeouts on "x86 Ubuntu Shared 3.x" buildbot #67959
Comments
First timeout: This build was only triggered by one changeset 0b99d7043a99: "Issue bpo-23694: Enhance _Py_open(), it now raises exceptions".
Example of subprocess timeout: Example of multiprocessing timeout: Thread 0x58a5ab40 (most recent call first): (...) Thread 0x55aaedc0 (most recent call first): |
test_multiprocessing_spawn.test_notify_all() also hangs on "AMD64 Debian root 3.x" buildbot: http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.x/builds/1959/steps/test/logs/stdio Thread 0x00002b303d918700 (most recent call first): Thread 0x00002b3060947700 (most recent call first): Thread 0x00002b303289db20 (most recent call first): |
A new failure test_subprocess.test_double_close_on_error: http://buildbot.python.org/all/builders/x86%20Ubuntu%20Shared%203.x/builds/11411/steps/test/logs/stdio |
@Haypo: I didn't think that one through -- the consequences of that fragile test are not a hang. It's unrelated. |
I was reproduce to issue on a buildbot and I got access to the buildbot. Using gdb, I saw that a process was stuck in _close_open_fds_safe(). The problem is that this function is called after fork() to run a child process. It's not safe to play with the GIL here. This bug is the regression which makes some buildbots to hang. I fixed the bug in the changeset 2e1234208bab. I keep the issue open a few days to check if buildbots are repaired or not. |
Last 5 builds of "x86 Ubuntu Shared 3.x" and "AMD64 Debian root 3.x" buildbots are green (success). The sporadic hang is gone! I close the issue. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: