You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2015/07/15 02:54:04 UTC
[jira] [Updated] (MESOS-3049) Failing CGROUPS_ROOT_PerfRollForward
test
[ https://issues.apache.org/jira/browse/MESOS-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam B updated MESOS-3049:
--------------------------
Affects Version/s: 0.23.0
Target Version/s: 0.23.0
Environment:
CentOS Linux release 7.1.1503
0.23.0-rc3
> Failing CGROUPS_ROOT_PerfRollForward test
> -----------------------------------------
>
> Key: MESOS-3049
> URL: https://issues.apache.org/jira/browse/MESOS-3049
> Project: Mesos
> Issue Type: Bug
> Components: containerization, test
> Affects Versions: 0.23.0
> Environment: CentOS Linux release 7.1.1503
> 0.23.0-rc3
> Reporter: Adam B
> Assignee: Timothy Chen
>
> {code}
> [ RUN ] MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
> I0715 00:28:42.600359 17919 exec.cpp:132] Version: 0.23.0
> I0715 00:28:42.609073 17983 exec.cpp:206] Executor registered on slave 20150715-002842-201330860-41108-794-S0
> Registered executor on srv2.hw.ca1.mesosphere.com
> Starting task b675699c-8427-4934-8bb5-62f91f3d74d0
> Forked command at 17988
> sh -c 'sleep 1000'
> ../../src/tests/slave_recovery_tests.cpp:3446: Failure
> containerizer2: Could not create isolator cgroups/perf_event: Failed to create PerfEvent isolator, invalid events: { cycles, task-clock }
> ../../3rdparty/libprocess/include/process/gmock.hpp:353: Failure
> Actual function call count doesn't match EXPECT_CALL(filter->mock, filter(testing::A<const DispatchEvent&>()))...
> Expected args: dispatch matcher (1-byte object <04>, 16-byte object <29-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00>)
> Expected: to be called once
> Actual: never called - unsatisfied and active
> [ FAILED ] MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward (462 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)