PortMapping tests are indeed in bade shape. There are JIRAs already, have a
look before filing new ones:
MESOS-4646, MESOS-5687, MESOS-2765, MESOS-5690, MESOS-5688, MESOS-5689,
MESOS-4643, MESOS-4644, MESOS-5309
On Sat, Jun 10, 2017 at 10:58 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> +1 (binding) Good enough for me.
>
> Ran `make check` (or equivalent) on the Mesosphere internal Jenkins CI.
> Lots of green (all tests passed) on Mac, CentOS7, Debian8, Fedora23 and
> Ubuntu 12.04.
> Three sets of yellow configs yielded 10 unique but mostly known
> failing/flaky tests.
> (Grey means untested)
> [image: Inline image 1]
>
> * Ubuntu {14.04|16.04|16.10} - {Plain|SSL|CMake|Clang}
> PerfTest.Version (always) - https://issues.apache.org/
> jira/browse/MESOS-7160
> ExamplesTest.PythonFramework (sometimes) - https://issues.apache.org/
> jira/browse/MESOS-7218
>
> * Centos 6 - {Plain|SSL}
> DockerContainerizerTest.ROOT_DOCKER_LaunchWithPersistentVolumes -
> https://issues.apache.org/jira/browse/MESOS-7510
>
> * Fedora 23 - Network_Isolator
> PortMappingIsolatorTest.ROOT_NC_HostToContainerUDP -
> https://issues.apache.org/jira/browse/MESOS-5690
> PortMappingIsolatorTest.ROOT_ContainerICMPExternal -
> https://issues.apache.org/jira/browse/MESOS-5689
> PortMappingIsolatorTest.ROOT_DNS - https://issues.apache.org/
> jira/browse/MESOS-5688
> PortMappingIsolatorTest.ROOT_NC_SmallEgressLimit -
> https://issues.apache.org/jira/browse/MESOS-5687
> PortMappingIsolatorTest.ROOT_NC_PortMappingStatistics - ?
> PortMappingMesosTest.CGROUPS_ROOT_RecoverMixedContainers - ?
> PortMappingMesosTest.CGROUPS_ROOT_RecoverMixedKnownAndUnKnownOrphans - ?
>
> Anybody have any ideas on the last three? Seems like these PortMapping
> tests are generally in a bad shape, or the network isolator is seriously
> broken. I'll file JIRAs.
>
> P.S. AgentAPIStreamingTest.AttachInputToNestedContainerSession Vinod saw
> on ASF CI is flaky according to https://issues.apache.org/jira
> /browse/MESOS-7159 (added the log gist link there)
>
> P.P.S. CI results at https://jenkins.mesosphere.
> com/service/jenkins/job/mesos/job/Mesos_CI-build/1215 for those with
> access. We're still working on exposing our CI to the public. Waiting is.
>
>
> On Thu, Jun 8, 2017 at 4:23 PM, Benjamin Mahler <bmah...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> make check passed on macOS 10.12.4
>>
>> The ContentType/AgentAPIStreamingTest.AttachInputToNestedContainerSession
>> passed for me. Kevin, I captured the logs to the failed run vinod pointed
>> to here:
>>
>> https://gist.github.com/bmahler/5ae340b4de3341f3c1f072250006dc64
>>
>> Does that look like a flaky test or a bug?
>>
>> On Thu, Jun 8, 2017 at 4:07 PM, Benjamin Mahler <bmah...@apache.org>
>> wrote:
>>
>>> Vinod I think that's the getenv issue from: https://issues.apache.or
>>> g/jira/browse/MESOS-6985
>>>
>>> On Wed, May 17, 2017 at 5:57 PM, Till Toenshoff <toensh...@me.com>
>>> wrote:
>>>
>>>> +1
>>>>
>>>> Ran it through DC/OS builds and integration tests;
>>>> https://github.com/dcos/dcos/pull/1530 => all green
>>>>
>>>> On May 17, 2017, at 10:01 PM, Vinod Kone <vinodk...@apache.org> wrote:
>>>>
>>>> Ran it on ASF CI and saw some issues.
>>>>
>>>> Segfault in "MasterTest.MultipleExecutors" in two builds [1]
>>>> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/35/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos:7,label_exp=%28docker%7C%7CHadoop%29&&%28%21ubuntu-us1%29&&%28%21ubuntu-eu2%29/consoleFull>
>>>> [2
>>>> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/35/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos:7,label_exp=%28docker%7C%7CHadoop%29&&%28%21ubuntu-us1%29&&%28%21ubuntu-eu2%29/console>],
>>>> which is concerning. Is this a known issue?
>>>>
>>>> "ContentType/AgentAPIStreamingTest.AttachInputToNestedContainerSession"
>>>> test failed
>>>> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/35/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=%28docker%7C%7CHadoop%29&&%28%21ubuntu-us1%29&&%28%21ubuntu-eu2%29/consoleFull>.
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, May 14, 2017 at 12:55 AM, tommy xiao <xia...@gmail.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> 2017-05-12 7:33 GMT+08:00 Adam Bordelon <a...@mesosphere.io>:
>>>>>
>>>>> > Hi all,
>>>>> >
>>>>> > Please vote on releasing the following candidate as Apache Mesos
>>>>> 1.2.1.
>>>>> >
>>>>> > 1.2.1 is a bug fix release. 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=1.2.1-rc1
>>>>> >
>>>>> > The candidate for Mesos 1.2.1 release is available at:
>>>>> > https://dist.apache.org/repos/dist/dev/mesos/1.2.1-rc1/mesos
>>>>> -1.2.1.tar.gz
>>>>> >
>>>>> > The tag to be voted on is 1.2.1-rc1:
>>>>> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit
>>>>> ;h=1.2.1-rc1
>>>>> >
>>>>> > The MD5 checksum of the tarball can be found at:
>>>>> > https://dist.apache.org/repos/dist/dev/mesos/1.2.1-rc1/
>>>>> > mesos-1.2.1.tar.gz.md5
>>>>> >
>>>>> > The signature of the tarball can be found at:
>>>>> > https://dist.apache.org/repos/dist/dev/mesos/1.2.1-rc1/
>>>>> > mesos-1.2.1.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/orgapache
>>>>> mesos-1192
>>>>> >
>>>>> > Please vote on releasing this package as Apache Mesos 1.2.1!
>>>>> >
>>>>> > The vote is open until Tue May 16 17:00 PDT 2017 and passes if a
>>>>> majority
>>>>> > of at least 3 +1 PMC votes are cast.
>>>>> >
>>>>> > [ ] +1 Release this package as Apache Mesos 1.2.1
>>>>> > [ ] -1 Do not release this package because ...
>>>>> >
>>>>> > Thanks,
>>>>> > -Adam-
>>>>> >
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Deshi Xiao
>>>>> Twitter: xds2000
>>>>> E-mail: xiaods(AT)gmail.com
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>
