Vinod Kone created MESOS-1699: --------------------------------- Summary: OsTest(s) sometimes are stuck forever Key: MESOS-1699 URL: https://issues.apache.org/jira/browse/MESOS-1699 Project: Mesos Issue Type: Bug Components: test Affects Versions: 0.20.0 Reporter: Vinod Kone
Observed this quite a few times on the Apache CI. The tests timeout somewhere in the OsTests. E.g: https://builds.apache.org/job/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Disable-Java-Disable-Python-Disable-Webui/2310/consoleText {code} [----------] 20 tests from OsTest [ RUN ] OsTest.find [ OK ] OsTest.find (1 ms) [ RUN ] OsTest.system sh: 1: invalid.command: not found [ OK ] OsTest.system (43 ms) [ RUN ] OsTest.release [ OK ] OsTest.release (1 ms) [ RUN ] OsTest.sysname [ OK ] OsTest.sysname (0 ms) [ RUN ] OsTest.uname [ OK ] OsTest.uname (0 ms) [ RUN ] OsTest.process [ OK ] OsTest.process (0 ms) [ RUN ] OsTest.touch [ OK ] OsTest.touch (1 ms) [ RUN ] OsTest.pstree Build timed out (after 180 minutes). Marking the build as failed. Build was aborted Sending e-mails to: d...@mesos.apache.org benjamin.hind...@gmail.com make[5]: *** wait: No child processes. Stop. make[5]: *** Waiting for unfinished jobs.... make[5]: *** wait: No child processes. Stop. make[3]: make[2]: *** [check-recursive] Terminated *** [check-recursive] Terminated make[4]: *** [check] Error 2 make: *** [check-recursive] Terminated make[1]: *** [check] Terminated Finished: FAILURE {code} -- This message was sent by Atlassian JIRA (v6.2#6252)