Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upShould wptrunner send a SIGTERM or SIGINT instead of SIGKILL when a timeout occurs? #14180
Labels
Comments
|
In my experience, the stack traces from timeouts are rarely meaningful - it's usually just sitting in an event loop somewhere, and not showing any kind of smoking gun. |
|
So is there anything to do here, or can we close this? |
|
It would require modifying . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It'd be helpful to get a backtrace when an unexpected timeout occurs, like in #13641.
Of course another timeout needs to be used to kill the process completely if it's unresponsive, but I expect that to be easy-ish...
Thoughts? @jdm @jgraham