Skip to content
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

Should wptrunner send a SIGTERM or SIGINT instead of SIGKILL when a timeout occurs? #14180

Open
emilio opened this issue Nov 12, 2016 · 3 comments
Open
Labels

Comments

@emilio
Copy link
Member

@emilio emilio commented Nov 12, 2016

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

@jdm
Copy link
Member

@jdm jdm commented Nov 12, 2016

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.

@nox
Copy link
Member

@nox nox commented Oct 7, 2017

So is there anything to do here, or can we close this?

@jdm
Copy link
Member

@jdm jdm commented Oct 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.