You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2016/02/23 20:41:18 UTC
[jira] [Created] (MESOS-4747)
ContainerLoggerTest.MesosContainerizerRecover cannot be executed in
isolation
Benjamin Bannier created MESOS-4747:
---------------------------------------
Summary: ContainerLoggerTest.MesosContainerizerRecover cannot be executed in isolation
Key: MESOS-4747
URL: https://issues.apache.org/jira/browse/MESOS-4747
Project: Mesos
Issue Type: Bug
Components: tests
Reporter: Benjamin Bannier
Assignee: Benjamin Bannier
Some cleanup of spawned processes is missing in {{ContainerLoggerTest.MesosContainerizerRecover}} so that when the test is run in isolation the global teardown might find lingering processes.
{code}
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from ContainerLoggerTest
[ RUN ] ContainerLoggerTest.MesosContainerizerRecover
[ OK ] ContainerLoggerTest.MesosContainerizerRecover (13 ms)
[----------] 1 test from ContainerLoggerTest (13 ms total)
[----------] Global test environment tear-down
../../src/tests/environment.cpp:728: Failure
Failed
Tests completed with child processes remaining:
-+- 7112 /SOME/PATH/src/mesos/build/src/.libs/mesos-tests --gtest_filter=ContainerLoggerTest.MesosContainerizerRecover
\--- 7130 (sh)
[==========] 1 test from 1 test case ran. (23 ms total)
[ PASSED ] 1 test.
[ FAILED ] 0 tests, listed below:
0 FAILED TESTS
{code}
Observered on OS X with clang-trunk and an unoptimized build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)