Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
It looks like something broke in the way we capture stack traces when a test hangs. For example, in this run - https://concourse.apachegeode-ci.info/builds/4984, instead of stack dumps, we see this in callstacks-2018-10-12-22-30-07.txt.
Container: gracious_austin ********* Dumping stack for process OCI: OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \"jstack\": executable file not found in $PATH": unknown