+1
Run all tests on Ubuntu 14.04 (physical box, not a VM).
All tests pass (as regular user).
`sudo make distcheck` still fails with the following errors; I am assuming
these are known issues and not deemed to be blockers?
[ FAILED ] 9 tests, listed below:
[ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
[ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
[ FAILED ]
MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
[ FAILED ] CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
[ FAILED ] MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
[ FAILED ] MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
[ FAILED ] NsTest.ROOT_setns
[ FAILED ] PerfTest.ROOT_Events
[ FAILED ] PerfTest.ROOT_SamplePid
I tried to check out 0.22.1 and run the same tests, but it has several
failures and it complains about already existing cgroups hierarchies; so
I'm assuming the earlier test run left the system in an unclean state.
*Marco Massenzio*
*Distributed Systems Engineer*
On Tue, Jul 21, 2015 at 3:12 PM, Adam Bordelon a...@mesosphere.io wrote:
+1 (binding) to Mesos 0.23.0-rc4 as 0.23.0
As I mentioned before, for rc3, basic integration tests passed for Mesos 0
.23.0 on CoreOS with DCOS GUI/CLI, Marathon, Chronos, Spark, HDFS,
Cassandra, and Kafka.
We have been tracking the Ubuntu `sudo make check` failures in
https://issues.apache.org/jira/browse/MESOS-3079 and related CentOS ROOT_
test failures in https://issues.apache.org/jira/browse/MESOS-3050 (some
fixes already pulled into rc4).
After pulling down the latest master, including a series of test code only
fixes for MESOS-3079, `sudo make check` passed for me on Ubuntu 14.04,
excluding only ROOT_DOCKER_Launch_Executor_Bridged (segfault tracked in
MESOS-3123). There are at least two remaining test-only fixes tracked in
MESOS-3079, but none of these are critical for Mesos 0.23.0, so I'm not
inclined to call for a rc5. We can call out the ROOT_ test failures as a
known issue with the release.
Anybody else have any test results?
Please vote,
-Adam-
On Fri, Jul 17, 2015 at 8:18 PM, Marco Massenzio ma...@mesosphere.io
wrote:
I am almost sure (more like hoping) I'm missing something fundamental
here and/or there is some basic configuration missing on my box.
Running tests as root, causes a significant number of failures.
Has anyone else *ever* run tests as root in the last few weeks?
Here's the headline, the full log of the failed tests attached.
$ lsb_release -a
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID: Ubuntu
Description:*Ubuntu 14.04.2 LTS*
Release:14.04
Codename: *trusty*
$ sudo make -j12 V=0 check
[==] 712 tests from 116 test cases ran. (318672 ms total)
[ PASSED ] 676 tests.
[ FAILED ] 36 tests, listed below:
[ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
[ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
[ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
mesos::internal::slave::MesosContainerizer
[ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where
TypeParam = mesos::internal::slave::MesosContainerizer
[ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
mesos::internal::slave::MesosContainerizer
[ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where
TypeParam = mesos::internal::slave::MesosContainerizer
[ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where
TypeParam = mesos::internal::slave::MesosContainerizer
[ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where
TypeParam = mesos::internal::slave::MesosContainerizer
[
