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.

Sign up for GitHub

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

Jump to bottom

Implement true heartbeat from the forked JVM #236

Open

dweiss opened this issue Oct 12, 2016 · 1 comment

Labels

ant-junit4 backwards_incompatible feature maven-junit4 refactoring

Contributor

dweiss commented Oct 12, 2016

A "true" heartbeat would provide several answers to problems we're currently facing:

it's not known where the "deadlocked" JVM actually is (stack traces),
it's not known whether it's a resource (no cpu usage) or active (spinloop) deadlock, sending back the stack traces a few time could answer this (as well as maybe generic CPU load),
it's not known whether the forked process is still alive at all (should heartbeat messages stop arriving, we can try to terminate the forked process and end with a build error).

dweiss added feature refactoring ant-junit4 maven-junit4 backwards_incompatible labels

dweiss added this to the 2.4.0 milestone

Contributor Author

dweiss commented Oct 12, 2016

This should provide some help in diagnosing issues like GH-233 too, hopefully.

dweiss modified the milestones: 2.5.0, 2.4.0

dweiss modified the milestones: 2.6., 2.5.0, 2.6.0

dweiss removed this from the 2.6.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment