[MESOS-4747] ContainerLoggerTest.MesosContainerizerRecover cannot be executed in isolation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.28.0
• Component/s: test
• Labels: mesosphere
• Epic Link: parallel-tests
• Sprint: Mesosphere Sprint 29
• Story Points: 1
• Assignee: Benjamin Bannier
• Reporter: Benjamin Bannier
• Shepherd: Adam B
• Created: 23/Feb/16 19:40
• Updated: 26/Nov/18 09:26
• Resolved: 26/Nov/18 09:26

Description

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.

[==========] 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

Observered on OS X with clang-trunk and an unoptimized build.