You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Jiang Yan Xu (JIRA)" <ji...@apache.org> on 2013/06/24 21:06:21 UTC
[jira] [Commented] (MESOS-520) ReaperTest.ChildProcess is flaky on
Jenkins.
[ https://issues.apache.org/jira/browse/MESOS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692263#comment-13692263 ]
Jiang Yan Xu commented on MESOS-520:
------------------------------------
This should be due to the change of semantics of Try<bool> os::alive() which now excludes the zombie state as the condition for a "true" return value.
> ReaperTest.ChildProcess is flaky on Jenkins.
> --------------------------------------------
>
> Key: MESOS-520
> URL: https://issues.apache.org/jira/browse/MESOS-520
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
> Assignee: Jiang Yan Xu
>
> [ RUN ] ReaperTest.ChildProcess
> I0624 02:39:29.119551 23272 reaper_tests.cpp:146] Child process 23386
> W0624 02:39:29.123200 23299 reaper.cpp:145] Cannot get the exit status of process 23386 because it is not a child of the calling process: Success
> ../../src/tests/reaper_tests.cpp:172: Failure
> status.get() is NONE
> [ FAILED ] ReaperTest.ChildProcess (14 ms)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira