mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Bordelon <a...@mesosphere.io>
Subject Re: [VOTE] Release Apache Mesos 0.23.0 (rc4)
Date Tue, 21 Jul 2015 22:12:49 GMT
+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 <marco@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
> [  FAILED  ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.NonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.PartitionedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.MasterFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.MultipleFrameworks, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.MultipleSlaves, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [  FAILED  ] SlaveRecoveryTest/0.RestartBeforeContainerizerLaunch, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [  FAILED  ] MesosContainerizerSlaveRecoveryTest.ResourceStatistics
> [  FAILED  ]
> MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
> [  FAILED  ]
> MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PidNamespaceForward
> [  FAILED  ]
> MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PidNamespaceBackward
> [  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
>
> 36 FAILED TESTS
>   YOU HAVE 12 DISABLED TESTS
>
>
>
> *Marco Massenzio*
> *Distributed Systems Engineer*
>
> On Fri, Jul 17, 2015 at 7:26 PM, Marco Massenzio <marco@mesosphere.io>
> wrote:
>
>> Ubuntu 14.04
>>
>> Not sure if I'm doing something wrong, `sudo make distcheck` fails -
>> re-running after a `make clean`
>>
>> If it continues failing, I'll provide more detailed log output.
>> In the meantime, if anyone has any suggestions as to what I may be doing
>> wrong, please let me know.
>>
>> $ ../configure && make -j8 V=0 && make -j12 V=0 check
>>
>> [==========] 649 tests from 94 test cases ran. (254152 ms total)
>> [  PASSED  ] 649 tests.
>>
>> $ sudo make -j12 V=0 distcheck
>>
>> [==========] 712 tests from 116 test cases ran. (325751 ms total)
>> [  PASSED  ] 702 tests.
>> [  FAILED  ] 10 tests, listed below:
>> [  FAILED  ] LimitedCpuIsolatorTest.ROOT_CGROUPS_Pids_and_Tids
>> [  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
>>
>> 10 FAILED TESTS
>>   YOU HAVE 12 DISABLED TESTS
>>
>>
>> *Marco Massenzio*
>> *Distributed Systems Engineer*
>>
>> On Fri, Jul 17, 2015 at 6:49 PM, Vinod Kone <vinodkone@gmail.com> wrote:
>>
>>> +1 (binding)
>>>
>>> Successfully built RPMs for CentOS5 and CentOS6 with network isolator.
>>>
>>>
>>> On Fri, Jul 17, 2015 at 4:56 PM, Khanduja, Vaibhav <
>>> vaibhav.khanduja@emc.com
>>> > wrote:
>>>
>>> > +1
>>> >
>>> > Sent from my iPhone. Please excuse the typos and brevity of this
>>> message.
>>> >
>>> > > On Jul 17, 2015, at 4:43 PM, Adam Bordelon <adam@mesosphere.io>
>>> wrote:
>>> > >
>>> > > Hello Mesos community,
>>> > >
>>> > > Please vote on releasing the following candidate as Apache Mesos
>>> 0.23.0.
>>> > >
>>> > > 0.23.0 includes the following:
>>> > >
>>> >
>>> --------------------------------------------------------------------------------
>>> > > - Per-container network isolation
>>> > > - Dockerized slaves will properly recover Docker containers upon
>>> > failover.
>>> > > - Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
>>> > >
>>> > > as well as experimental support for:
>>> > > - Fetcher Caching
>>> > > - Revocable Resources
>>> > > - SSL encryption
>>> > > - Persistent Volumes
>>> > > - Dynamic Reservations
>>> > >
>>> > > The CHANGELOG for the release is available at:
>>> > >
>>> >
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.23.0-rc4
>>> > >
>>> >
>>> --------------------------------------------------------------------------------
>>> > >
>>> > > The candidate for Mesos 0.23.0 release is available at:
>>> > >
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc4/mesos-0.23.0.tar.gz
>>> > >
>>> > > The tag to be voted on is 0.23.0-rc4:
>>> > >
>>> >
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc4
>>> > >
>>> > > The MD5 checksum of the tarball can be found at:
>>> > >
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc4/mesos-0.23.0.tar.gz.md5
>>> > >
>>> > > The signature of the tarball can be found at:
>>> > >
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc4/mesos-0.23.0.tar.gz.asc
>>> > >
>>> > > The PGP key used to sign the release is here:
>>> > > https://dist.apache.org/repos/dist/release/mesos/KEYS
>>> > >
>>> > > The JAR is up in Maven in a staging repository here:
>>> > >
>>> https://repository.apache.org/content/repositories/orgapachemesos-1062
>>> > >
>>> > > Please vote on releasing this package as Apache Mesos 0.23.0!
>>> > >
>>> > > The vote is open until Wed July 22nd, 17:00 PDT 2015 and passes if
a
>>> > > majority of at least 3 +1 PMC votes are cast.
>>> > >
>>> > > [ ] +1 Release this package as Apache Mesos 0.23.0 (I've tested it!)
>>> > > [ ] -1 Do not release this package because ...
>>> > >
>>> > > Thanks,
>>> > > -Adam-
>>> >
>>>
>>
>>
>

Mime
View raw message