You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Paul Brett (JIRA)" <ji...@apache.org> on 2015/08/13 02:07:46 UTC
[jira] [Updated] (MESOS-3254) Cgroup CHECK fails test harness
[ https://issues.apache.org/jira/browse/MESOS-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Brett updated MESOS-3254:
------------------------------
Description:
CHECK in clean up of ContainerizerTest causes test harness to abort rather than fail or skip only perf related tests.
[ RUN ] SlaveRecoveryTest/0.RestartBeforeContainerizerLaunch
[ OK ] SlaveRecoveryTest/0.RestartBeforeContainerizerLaunch (628 ms)
[----------] 24 tests from SlaveRecoveryTest/0 (38986 ms total)
[----------] 4 tests from MesosContainerizerSlaveRecoveryTest
[ RUN ] MesosContainerizerSlaveRecoveryTest.ResourceStatistics
../../src/tests/mesos.cpp:720: Failure
cgroups::mount(hierarchy, subsystem): 'perf_event' is already attached to another hierarchy
-------------------------------------------------------------
We cannot run any cgroups tests that require
a hierarchy with subsystem 'perf_event'
because we failed to find an existing hierarchy
or create a new one (tried '/tmp/mesos_test_cgroup/perf_event').
You can either remove all existing
hierarchies, or disable this test case
(i.e., --gtest_filter=-MesosContainerizerSlaveRecoveryTest.*).
-------------------------------------------------------------
F0811 17:23:43.874696 12955 mesos.cpp:774] CHECK_SOME(cgroups): '/tmp/mesos_test_cgroup/perf_event' is not a valid hierarchy
*** Check failure stack trace: ***
@ 0x7fb2fb4835fd google::LogMessage::Fail()
@ 0x7fb2fb48543d google::LogMessage::SendToLog()
@ 0x7fb2fb4831ec google::LogMessage::Flush()
@ 0x7fb2fb485d39 google::LogMessageFatal::~LogMessageFatal()
@ 0x4e3f98 _CheckFatal::~_CheckFatal()
@ 0x82f25a mesos::internal::tests::ContainerizerTest<>::TearDown()
@ 0xc030e3 testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0xbf9050 testing::Test::Run()
@ 0xbf912e testing::TestInfo::Run()
@ 0xbf9235 testing::TestCase::Run()
@ 0xbf94e8 testing::internal::UnitTestImpl::RunAllTests()
@ 0xbf97a4 testing::UnitTest::Run()
@ 0x4a9df3 main
@ 0x7fb2f9371ec5 (unknown)
@ 0x4b63ee (unknown)
Build step 'Execute shell' marked build as failure
was:
CHECK in clean up of ContainerizerTest causes test harness to abort rather than fail or skip only perf related tests.
[ RUN ] SlaveRecoveryTest/0.RestartBeforeContainerizerLaunch
[ OK ] SlaveRecoveryTest/0.RestartBeforeContainerizerLaunch (628 ms)
[----------] 24 tests from SlaveRecoveryTest/0 (38986 ms total)
[----------] 4 tests from MesosContainerizerSlaveRecoveryTest
[ RUN ] MesosContainerizerSlaveRecoveryTest.ResourceStatistics
../../src/tests/mesos.cpp:720: Failure
cgroups::mount(hierarchy, subsystem): 'perf_event' is already attached to another hierarchy
-------------------------------------------------------------
We cannot run any cgroups tests that require
a hierarchy with subsystem 'perf_event'
because we failed to find an existing hierarchy
or create a new one (tried '/tmp/mesos_test_cgroup/perf_event').
You can either remove all existing
hierarchies, or disable this test case
(i.e., --gtest_filter=-MesosContainerizerSlaveRecoveryTest.*).
-------------------------------------------------------------
F0811 17:23:43.874696 12955 mesos.cpp:774] CHECK_SOME(cgroups): '/tmp/mesos_test_cgroup/perf_event' is not a valid hierarchy
*** Check failure stack trace: ***
@ 0x7fb2fb4835fd google::LogMessage::Fail()
@ 0x7fb2fb48543d google::LogMessage::SendToLog()
@ 0x7fb2fb4831ec google::LogMessage::Flush()
@ 0x7fb2fb485d39 google::LogMessageFatal::~LogMessageFatal()
@ 0x4e3f98 _CheckFatal::~_CheckFatal()
@ 0x82f25a mesos::internal::tests::ContainerizerTest<>::TearDown()
@ 0xc030e3 testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0xbf9050 testing::Test::Run()
@ 0xbf912e testing::TestInfo::Run()
@ 0xbf9235 testing::TestCase::Run()
@ 0xbf94e8 testing::internal::UnitTestImpl::RunAllTests()
@ 0xbf97a4 testing::UnitTest::Run()
@ 0x4a9df3 main
@ 0x7fb2f9371ec5 (unknown)
@ 0x4b63ee (unknown)
Build step 'Execute shell' marked build as failure
> Cgroup CHECK fails test harness
> -------------------------------
>
> Key: MESOS-3254
> URL: https://issues.apache.org/jira/browse/MESOS-3254
> Project: Mesos
> Issue Type: Bug
> Components: test
> Reporter: Paul Brett
>
> CHECK in clean up of ContainerizerTest causes test harness to abort rather than fail or skip only perf related tests.
> [ RUN ] SlaveRecoveryTest/0.RestartBeforeContainerizerLaunch
> [ OK ] SlaveRecoveryTest/0.RestartBeforeContainerizerLaunch (628 ms)
> [----------] 24 tests from SlaveRecoveryTest/0 (38986 ms total)
> [----------] 4 tests from MesosContainerizerSlaveRecoveryTest
> [ RUN ] MesosContainerizerSlaveRecoveryTest.ResourceStatistics
> ../../src/tests/mesos.cpp:720: Failure
> cgroups::mount(hierarchy, subsystem): 'perf_event' is already attached to another hierarchy
> -------------------------------------------------------------
> We cannot run any cgroups tests that require
> a hierarchy with subsystem 'perf_event'
> because we failed to find an existing hierarchy
> or create a new one (tried '/tmp/mesos_test_cgroup/perf_event').
> You can either remove all existing
> hierarchies, or disable this test case
> (i.e., --gtest_filter=-MesosContainerizerSlaveRecoveryTest.*).
> -------------------------------------------------------------
> F0811 17:23:43.874696 12955 mesos.cpp:774] CHECK_SOME(cgroups): '/tmp/mesos_test_cgroup/perf_event' is not a valid hierarchy
> *** Check failure stack trace: ***
> @ 0x7fb2fb4835fd google::LogMessage::Fail()
> @ 0x7fb2fb48543d google::LogMessage::SendToLog()
> @ 0x7fb2fb4831ec google::LogMessage::Flush()
> @ 0x7fb2fb485d39 google::LogMessageFatal::~LogMessageFatal()
> @ 0x4e3f98 _CheckFatal::~_CheckFatal()
> @ 0x82f25a mesos::internal::tests::ContainerizerTest<>::TearDown()
> @ 0xc030e3 testing::internal::HandleExceptionsInMethodIfSupported<>()
> @ 0xbf9050 testing::Test::Run()
> @ 0xbf912e testing::TestInfo::Run()
> @ 0xbf9235 testing::TestCase::Run()
> @ 0xbf94e8 testing::internal::UnitTestImpl::RunAllTests()
> @ 0xbf97a4 testing::UnitTest::Run()
> @ 0x4a9df3 main
> @ 0x7fb2f9371ec5 (unknown)
> @ 0x4b63ee (unknown)
> Build step 'Execute shell' marked build as failure
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)