[
https://issues.apache.org/jira/browse/MESOS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790760#comment-13790760
]
Benjamin Mahler commented on MESOS-685:
---------------------------------------
The JVM SIGSEGV appears to be a result of the test failing, rather than the
cause.
For SlaveRecoveryTest/RecoveryTimeout, we were stopping and starting the slave
process, and expecting the executor driver (in a separate unix process) to
receive an exited() notification. This is actually not supported in libprocess.
See {{3rdparty/libprocess/TODO}}:
{code}
/* TODO(benh): Fix link functionality (processes need to send
process_exit message since a dead process on one node might not
know that a process on another node linked with it). */
{code}
> SlaveRecoveryTest/0.RecoveryTimeout Java SIGSEGV
> ------------------------------------------------
>
> Key: MESOS-685
> URL: https://issues.apache.org/jira/browse/MESOS-685
> Project: Mesos
> Issue Type: Bug
> Components: test
> Affects Versions: 0.14.0
> Environment: Linux
> Reporter: Vinson Lee
> Assignee: Benjamin Mahler
> Fix For: 0.14.0
>
> Attachments: hs_err_pid2204.log
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
