[jira] [Commented] (MESOS-3421) Support sharing persistent volumes across task instances
[ https://issues.apache.org/jira/browse/MESOS-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908119#comment-14908119 ] Artem Harutyunyan commented on MESOS-3421: -- This tickets needs a shepherd before we can accept it. > Support sharing persistent volumes across task instances > > > Key: MESOS-3421 > URL: https://issues.apache.org/jira/browse/MESOS-3421 > Project: Mesos > Issue Type: Improvement > Components: general >Affects Versions: 0.23.0 >Reporter: Anindya Sinha >Assignee: Anindya Sinha > > A service that needs persistent volume needs to have access to the same > persistent volume (RW) from multiple task(s) instances on the same agent > node. Currently, a persistent volume once offered to the framework(s) can be > scheduled to a task and until that tasks terminates, that persistent volume > cannot be used by another task. > Explore providing the capability of sharing persistent volumes across task > instances scheduled on a single agent node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3502) Create Benchmark for Value::Ranges.
[ https://issues.apache.org/jira/browse/MESOS-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-3502: - Labels: mesosphere (was: ) > Create Benchmark for Value::Ranges. > --- > > Key: MESOS-3502 > URL: https://issues.apache.org/jira/browse/MESOS-3502 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad > Labels: mesosphere > > When refactoring the Value::Ranges Code for Mesos-3051 we used a proprietary > benchmark to measure the results. > We need to develop an open-source benchmark for measuring the performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3454) Remove duplicated logic in Flags::load
[
https://issues.apache.org/jira/browse/MESOS-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908134#comment-14908134
]
Artem Harutyunyan commented on MESOS-3454:
--
Can we get a shepherd for this one before accepting?
> Remove duplicated logic in Flags::load
> --
>
> Key: MESOS-3454
> URL: https://issues.apache.org/jira/browse/MESOS-3454
> Project: Mesos
> Issue Type: Bug
> Components: stout
>Reporter: Klaus Ma
>Priority: Minor
>
> In {{flags.hpp}}, there are two functions with almost the same logic; this
> ticket is used to merge the duplicated part.
> {code}
> inline Try FlagsBase::load(
> const Option& prefix,
> int* argc,
> char*** argv,
> bool unknowns,
> bool duplicates)
> ...
> inline Try FlagsBase::load(
> const Option& prefix,
> int argc,
> const char* const *argv,
> bool unknowns,
> bool duplicates)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3462) Containerization issues with mesos running on CoreOS
[
https://issues.apache.org/jira/browse/MESOS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908126#comment-14908126
]
Artem Harutyunyan commented on MESOS-3462:
--
This does not sound like a Mesos issue.
> Containerization issues with mesos running on CoreOS
>
>
> Key: MESOS-3462
> URL: https://issues.apache.org/jira/browse/MESOS-3462
> Project: Mesos
> Issue Type: Bug
> Components: containerization
>Affects Versions: 0.24.0
> Environment: CoreOS 801.0.0 64-bit
>Reporter: Francis Chuang
>Assignee: haosdent
>
> These are the steps to I used to build mesos 0.24.0 on Ubuntu 15.04 64-bit:
> wget http://www.apache.org/dist/mesos/0.24.0/mesos-0.24.0.tar.gz
> wget http://mirror.ventraip.net.au/apache/apr/apr-1.5.2.tar.gz
> wget http://mirror.ventraip.net.au/apache/apr/apr-util-1.5.4.tar.gz
> wget http://mirror.ventraip.net.au/apache/subversion/subversion-1.9.0.tar.gz
> wget http://www.sqlite.org/sqlite-amalgamation-3071501.zip
> wget ftp://ftp.cyrusimap.org/cyrus-sasl/cyrus-sasl-2.1.26.tar.gz
> mkdir /tmp/mesos-build
> cd /tmp/mesos-build
> - Build apr
> tar zxf apr-$APR_VERSION.tar.gz
> cd apr-$APR_VERSION
> ./configure CC=gcc-4.8 --prefix=/tmp/mesos-build/apr
> make
> make install
> cd ..
> - Build apr-util
> tar zxf apr-util-$APR_UTIL_VERSION.tar.gz
> cd apr-util-$APR_UTIL_VERSION
> ./configure CC=gcc-4.8 --prefix=/tmp/mesos-build/apr-util
> --with-apr=/tmp/mesos-build/apr
> make
> make install
> cd ..
> - Build libsasl2
> tar zxf cyrus-sasl-$SASL_VERSION.tar.gz
> cd cyrus-sasl-$SASL_VERSION
> ./configure CC=gcc-4.8 CPPFLAGS=-I/usr/include/openssl
> --prefix=/tmp/mesos-build/sasl2 --enable-cram
> make
> make install
> cd ..
> - Build subversion
> tar zxf subversion-$SVN_VERSION.tar.gz
> unzip sqlite-amalgamation-$SQLITE_AMALGATION_VERSION.zip
> mv sqlite-amalgamation-$SQLITE_AMALGATION_VERSION/
> subversion-$SVN_VERSION/sqlite-amalgamation/
> cd subversion-$SVN_VERSION
> ./configure CC=gcc-4.8 CXX=g++-4.8 --prefix=/tmp/mesos-build/svn
> --with-apr=/tmp/mesos-build/apr --with-apr-util=/tmp/mesos-build/apr-util
> --with-sasl=/tmp/mesos-build/sasl2
> make
> make install
> cd ..
> - Build curl
> tar zxf curl-$CURL_VERSION.tar.gz
> cd curl-$CURL_VERSION
> ./configure CC=gcc-4.8 --prefix=/tmp/mesos-build/curl
> make
> make install
> cd ..
> - Build mesos
> tar zxf mesos-$MESOS_VERSION.tar.gz
> cd mesos-$MESOS_VERSION
> mkdir build
> cd build
> ../configure CC=gcc-4.8 CXX=g++-4.8
> LD_LIBRARY_PATH=/tmp/mesos-build/sasl2/lib
> SASL_PATH=/tmp/mesos-build/sasl2/lib/sasl2 --prefix=/tmp/mesos-build/mesos
> --with-svn=/tmp/mesos-build/svn --with-apr=/tmp/mesos-build/apr
> --with-sasl=/tmp/mesos-build/sasl2/ --with-curl=/tmp/mesos-build/curl
> make
> make install
> cd ..
> cd ..
> - Copy shared objects into mesos build
> cp apr/lib/libapr-1.so.0.5.2 mesos/lib/libapr-1.so.0
> cp apr-util/lib/libaprutil-1.so.0.5.4 mesos/lib/libaprutil-1.so.0
> cp sasl2/lib/libsasl2.so.3.0.0 mesos/lib/libsasl2.so.3
> cp svn/lib/libsvn_delta-1.so.0.0.0 mesos/lib/libsvn_delta-1.so.0
> cp svn/lib/libsvn_subr-1.so.0.0.0 mesos/lib/libsvn_subr-1.so.0
> I then compress the build into an archive and distributed it onto my CoreOS
> nodes.
> Once I have the archive extracted on each node, I start the master and slaves:
> /opt/mesos/sbin/mesos-master --zk=zk://192.168.33.10/mesos --quorum=1
> --hostname=192.168.33.10 --ip=192.168.33.10
> --webui_dir=/opt/mesos/share/mesos/webui --cluster=mesos
> /opt/mesos/sbin/mesos-slave --hostname=192.168.33.11 --ip=192.168.33.11
> --master=zk://192.168.33.10/mesos
> --executor_environment_variables='{"LD_LIBRARY_PATH": "/opt/mesos/lib",
> "PATH": "/opt/java/bin:/usr/sbin:/usr/bin"}' --containerizers=docker,mesos
> --executor_registration_timeout=60mins
> --launcher_dir=/opt/mesos/libexec/mesos/
> In addition, the following environment variables are set:
> LD_LIBRARY_PATH=/opt/mesos/lib/
> JAVA_HOME=/opt/java
> MESOS_NATIVE_JAVA_LIBRARY=/opt/mesos/lib/libmesos.so
> I am finding that when I run meso-hdfs from
> https://github.com/mesosphere/hdfs, the scheduler starts properly and
> launches the executors. However, the executors will fail and terminate
> without writing any error to stderr and stdout.
> I have reproduced the same problem with mesos 0.24, 0.23 and 0.22.1
> If I install mesos onto a Ubuntu machine (tried 14.04 and 15.04 64-bit) using
> the apt-repositories, this problem does not happen.
> I am not well-versed with mesos internals, but it was pointed out that it's
> most likely a containerization issue. This issue on github documents the
> process of trying to get mesos-hdfs to work on my compiled mesos binaries:
> https://github.com/mesosphere/hdfs/issues/194
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3421) Support sharing persistent volumes across task instances
[ https://issues.apache.org/jira/browse/MESOS-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908243#comment-14908243 ] Anindya Sinha commented on MESOS-3421: -- > 1.) prvoide a way for user to publish data's location/info Currently, the container_path is specified in the Offer::Operation::CREATE through the Volumes section of the protobuf (within DiskInfo). This is the path within the container, which is linked to physical volume (currently set in /volumes/roles//). Are you suggesting that the container_path should be set when LAUNCH happens as opposed to when CREATE happens? I think that might be a good enhancement to enable each task container specify its own container_path. > 2.) provide a way for user to share volume in slave hosts I think just because the framework picks up a persistent volume from the offer to schedule a task should be good to demonstrate an intention to use a volume - shared or non-shared. > Support sharing persistent volumes across task instances > > > Key: MESOS-3421 > URL: https://issues.apache.org/jira/browse/MESOS-3421 > Project: Mesos > Issue Type: Improvement > Components: general >Affects Versions: 0.23.0 >Reporter: Anindya Sinha >Assignee: Anindya Sinha > > A service that needs persistent volume needs to have access to the same > persistent volume (RW) from multiple task(s) instances on the same agent > node. Currently, a persistent volume once offered to the framework(s) can be > scheduled to a task and until that tasks terminates, that persistent volume > cannot be used by another task. > Explore providing the capability of sharing persistent volumes across task > instances scheduled on a single agent node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-3462) Containerization issues with mesos running on CoreOS
[
https://issues.apache.org/jira/browse/MESOS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908126#comment-14908126
]
Artem Harutyunyan edited comment on MESOS-3462 at 9/25/15 3:11 PM:
---
This does not sound like a Mesos issue. I'd suggest to close this ticket and
move the discussion to the mailing list or IRC.
was (Author: hartem):
This does not sound like a Mesos issue.
> Containerization issues with mesos running on CoreOS
>
>
> Key: MESOS-3462
> URL: https://issues.apache.org/jira/browse/MESOS-3462
> Project: Mesos
> Issue Type: Bug
> Components: containerization
>Affects Versions: 0.24.0
> Environment: CoreOS 801.0.0 64-bit
>Reporter: Francis Chuang
>Assignee: haosdent
>
> These are the steps to I used to build mesos 0.24.0 on Ubuntu 15.04 64-bit:
> wget http://www.apache.org/dist/mesos/0.24.0/mesos-0.24.0.tar.gz
> wget http://mirror.ventraip.net.au/apache/apr/apr-1.5.2.tar.gz
> wget http://mirror.ventraip.net.au/apache/apr/apr-util-1.5.4.tar.gz
> wget http://mirror.ventraip.net.au/apache/subversion/subversion-1.9.0.tar.gz
> wget http://www.sqlite.org/sqlite-amalgamation-3071501.zip
> wget ftp://ftp.cyrusimap.org/cyrus-sasl/cyrus-sasl-2.1.26.tar.gz
> mkdir /tmp/mesos-build
> cd /tmp/mesos-build
> - Build apr
> tar zxf apr-$APR_VERSION.tar.gz
> cd apr-$APR_VERSION
> ./configure CC=gcc-4.8 --prefix=/tmp/mesos-build/apr
> make
> make install
> cd ..
> - Build apr-util
> tar zxf apr-util-$APR_UTIL_VERSION.tar.gz
> cd apr-util-$APR_UTIL_VERSION
> ./configure CC=gcc-4.8 --prefix=/tmp/mesos-build/apr-util
> --with-apr=/tmp/mesos-build/apr
> make
> make install
> cd ..
> - Build libsasl2
> tar zxf cyrus-sasl-$SASL_VERSION.tar.gz
> cd cyrus-sasl-$SASL_VERSION
> ./configure CC=gcc-4.8 CPPFLAGS=-I/usr/include/openssl
> --prefix=/tmp/mesos-build/sasl2 --enable-cram
> make
> make install
> cd ..
> - Build subversion
> tar zxf subversion-$SVN_VERSION.tar.gz
> unzip sqlite-amalgamation-$SQLITE_AMALGATION_VERSION.zip
> mv sqlite-amalgamation-$SQLITE_AMALGATION_VERSION/
> subversion-$SVN_VERSION/sqlite-amalgamation/
> cd subversion-$SVN_VERSION
> ./configure CC=gcc-4.8 CXX=g++-4.8 --prefix=/tmp/mesos-build/svn
> --with-apr=/tmp/mesos-build/apr --with-apr-util=/tmp/mesos-build/apr-util
> --with-sasl=/tmp/mesos-build/sasl2
> make
> make install
> cd ..
> - Build curl
> tar zxf curl-$CURL_VERSION.tar.gz
> cd curl-$CURL_VERSION
> ./configure CC=gcc-4.8 --prefix=/tmp/mesos-build/curl
> make
> make install
> cd ..
> - Build mesos
> tar zxf mesos-$MESOS_VERSION.tar.gz
> cd mesos-$MESOS_VERSION
> mkdir build
> cd build
> ../configure CC=gcc-4.8 CXX=g++-4.8
> LD_LIBRARY_PATH=/tmp/mesos-build/sasl2/lib
> SASL_PATH=/tmp/mesos-build/sasl2/lib/sasl2 --prefix=/tmp/mesos-build/mesos
> --with-svn=/tmp/mesos-build/svn --with-apr=/tmp/mesos-build/apr
> --with-sasl=/tmp/mesos-build/sasl2/ --with-curl=/tmp/mesos-build/curl
> make
> make install
> cd ..
> cd ..
> - Copy shared objects into mesos build
> cp apr/lib/libapr-1.so.0.5.2 mesos/lib/libapr-1.so.0
> cp apr-util/lib/libaprutil-1.so.0.5.4 mesos/lib/libaprutil-1.so.0
> cp sasl2/lib/libsasl2.so.3.0.0 mesos/lib/libsasl2.so.3
> cp svn/lib/libsvn_delta-1.so.0.0.0 mesos/lib/libsvn_delta-1.so.0
> cp svn/lib/libsvn_subr-1.so.0.0.0 mesos/lib/libsvn_subr-1.so.0
> I then compress the build into an archive and distributed it onto my CoreOS
> nodes.
> Once I have the archive extracted on each node, I start the master and slaves:
> /opt/mesos/sbin/mesos-master --zk=zk://192.168.33.10/mesos --quorum=1
> --hostname=192.168.33.10 --ip=192.168.33.10
> --webui_dir=/opt/mesos/share/mesos/webui --cluster=mesos
> /opt/mesos/sbin/mesos-slave --hostname=192.168.33.11 --ip=192.168.33.11
> --master=zk://192.168.33.10/mesos
> --executor_environment_variables='{"LD_LIBRARY_PATH": "/opt/mesos/lib",
> "PATH": "/opt/java/bin:/usr/sbin:/usr/bin"}' --containerizers=docker,mesos
> --executor_registration_timeout=60mins
> --launcher_dir=/opt/mesos/libexec/mesos/
> In addition, the following environment variables are set:
> LD_LIBRARY_PATH=/opt/mesos/lib/
> JAVA_HOME=/opt/java
> MESOS_NATIVE_JAVA_LIBRARY=/opt/mesos/lib/libmesos.so
> I am finding that when I run meso-hdfs from
> https://github.com/mesosphere/hdfs, the scheduler starts properly and
> launches the executors. However, the executors will fail and terminate
> without writing any error to stderr and stdout.
> I have reproduced the same problem with mesos 0.24, 0.23 and 0.22.1
> If I install mesos onto a Ubuntu machine (tried 14.04 and 15.04 64-bit) using
> the apt-repositories, this problem does not happen.
> I am not well-versed with mesos internals, but it was pointed out that it's
> most likely a containerization issue. This issue on github documents the
> process of trying
[jira] [Commented] (MESOS-3467) Provide the users with a fully writable filesystem
[ https://issues.apache.org/jira/browse/MESOS-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908137#comment-14908137 ] Artem Harutyunyan commented on MESOS-3467: -- Can we please get a shepherd for this ticket? > Provide the users with a fully writable filesystem > -- > > Key: MESOS-3467 > URL: https://issues.apache.org/jira/browse/MESOS-3467 > Project: Mesos > Issue Type: Story >Reporter: Yan Xu > > In the first phase of filesystem provisioning and isolation we are > disallowing (or at least should, especially in the case of CopyBackend) users > to write outside the sandbox without explicitly mounting specific volumes > into the container. We do this even when OverlayBackend can potentially > support a empty writable top layer. > However in the real world use of containers (and for people coming from the > VM world), users and applications often are used to being able to write to > the full filesystem (restricted by plain file system permissions) with > reasons ranging from applications being non-portable (filesystem-wise) to the > need to do custom installs at run time to system directories (inside its > container). > In general, it's a good practice to restrict the application to write to > confined locations and software dependencies can be managed through > pre-packaged layers but these often introduce a high entry barrier for users. > We should discuss a solution that gives the users the option to write to a > full filesystem with a filesystem layer on top of provisioned images and > optionally enable persistence of that layer through persistent volumes. This > has implication in the management of user namespaces and resource > reservations and requires a thorough design. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3469) Replace hard code error message by typed error system
[ https://issues.apache.org/jira/browse/MESOS-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908142#comment-14908142 ] Artem Harutyunyan commented on MESOS-3469: -- Needs a shepherd. > Replace hard code error message by typed error system > -- > > Key: MESOS-3469 > URL: https://issues.apache.org/jira/browse/MESOS-3469 > Project: Mesos > Issue Type: Bug >Reporter: Klaus Ma > > Current, all message are hard code in the source code; it's better to be > enhanced by typed error system for : > - Internationalization > - Checking error code instead of string -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3413) Docker containerizer does not symlink persistent volumes into sandbox
[
https://issues.apache.org/jira/browse/MESOS-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907947#comment-14907947
]
Max Neunhöffer commented on MESOS-3413:
---
It seems to work for me now after I have done what haosdent suggests. Can
somebody point be to the code in mesos which does this magic? I am aware of the
code round line 382 in mesos-0.23-0/src/docker/docker.cpp taking care of
relative names in "host_path" entries of volumes. However, I do not understand
how the word I put into "container_path" in the volume I make persistent is
matched to the same word I put into "host_path" in the volume I mount when
launching the task, replacing the latter with the relative path to the actual
persistent volume...
> Docker containerizer does not symlink persistent volumes into sandbox
> -
>
> Key: MESOS-3413
> URL: https://issues.apache.org/jira/browse/MESOS-3413
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker, slave
>Affects Versions: 0.23.0
>Reporter: Max Neunhöffer
>Assignee: haosdent
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> For the ArangoDB framework I am trying to use the persistent primitives.
> nearly all is working, but I am missing a crucial piece at the end: I have
> successfully created a persistent disk resource and have set the persistence
> and volume information in the DiskInfo message. However, I do not see any way
> to find out what directory on the host the mesos slave has reserved for us. I
> know it is ${MESOS_SLAVE_WORKDIR}/volumes/roles//_ but we
> have no way to query this information anywhere. The docker containerizer does
> not automatically mount this directory into our docker container, or symlinks
> it into our sandbox. Therefore, I have essentially no access to it. Note that
> the mesos containerizer (which I cannot use for other reasons) seems to
> create a symlink in the sandbox to the actual path for the persistent volume.
> With that, I could mount the volume into our docker container and all would
> be well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3493) benchmark for declining offers
[ https://issues.apache.org/jira/browse/MESOS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joris Van Remoortere updated MESOS-3493: Shepherd: Joris Van Remoortere > benchmark for declining offers > -- > > Key: MESOS-3493 > URL: https://issues.apache.org/jira/browse/MESOS-3493 > Project: Mesos > Issue Type: Improvement > Components: test >Reporter: James Peach >Priority: Minor > > I wrote a benchmark that can be used to demonstrate the performance issues > addressed in MESOS-3052, MESOS-3051, MESOS-3157 and MESOS-3075. The benchmark > simulates a number of frameworks that start declining all offers once they > reach the limit of work they need to do. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3501) configure cannot find libevent headers in CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908478#comment-14908478
]
Greg Mann commented on MESOS-3501:
--
The homie Kartic found some CentOS 6 RPMs for libevent2, so we can include
those in the docs:
ftp://ftp.pbone.net/mirror/ftp5.gwdg.de/pub/opensuse/repositories/home:/kalyaka/CentOS_CentOS-6/x86_64/libevent2-2.0.21-11.1.x86_64.rpm
ftp://ftp.pbone.net/mirror/ftp5.gwdg.de/pub/opensuse/repositories/home:/kalyaka/CentOS_CentOS-6/x86_64/libevent2-devel-2.0.21-11.1.x86_64.rpm
> configure cannot find libevent headers in CentOS 6
> --
>
> Key: MESOS-3501
> URL: https://issues.apache.org/jira/browse/MESOS-3501
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: CentOS 6.6, 6.7
>Reporter: Greg Mann
>Assignee: Greg Mann
> Labels: build, configure, libevent, mesosphere
>
> If libevent is installed via {{sudo yum install libevent-headers}}, running
> {{../configure --enable-libevent}} will fail to discover the libevent headers:
> {code}
> checking event2/event.h usability... no
> checking event2/event.h presence... no
> checking for event2/event.h... no
> configure: error: cannot find libevent headers
> ---
> libevent is required for libprocess to build.
> ---
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3519) Fix file descriptor leakage in the code base
[ https://issues.apache.org/jira/browse/MESOS-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908634#comment-14908634 ] Chi Zhang commented on MESOS-3519: -- https://reviews.apache.org/r/38743/ > Fix file descriptor leakage in the code base > > > Key: MESOS-3519 > URL: https://issues.apache.org/jira/browse/MESOS-3519 > Project: Mesos > Issue Type: Bug >Reporter: Chi Zhang >Assignee: Chi Zhang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3519) Fix file descriptor leakage / double close in the code base
[ https://issues.apache.org/jira/browse/MESOS-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Zhang updated MESOS-3519: - Summary: Fix file descriptor leakage / double close in the code base (was: Fix file descriptor leakage in the code base) > Fix file descriptor leakage / double close in the code base > --- > > Key: MESOS-3519 > URL: https://issues.apache.org/jira/browse/MESOS-3519 > Project: Mesos > Issue Type: Bug >Reporter: Chi Zhang >Assignee: Chi Zhang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3521) Support for hardware topology and resources description
Jonathan Calmels created MESOS-3521:
---
Summary: Support for hardware topology and resources description
Key: MESOS-3521
URL: https://issues.apache.org/jira/browse/MESOS-3521
Project: Mesos
Issue Type: Improvement
Reporter: Jonathan Calmels
In heterogeneous clusters, tasks sometimes have strong constraints on the type
of hardware they need to execute on. The current solution is to use custom
attributes to describe resources on the agents.
While this solution works, the current attribute format is somehow constraining
and requires workarounds on both the agent and the scheduler (e.g. Base64 RFC
6920). In addition, we often need to encode the link between an attribute and a
resource which is inherently error prone and implementation defined from one
scheduler to another.
I would like to propose a unified format to expose hardware topology and
resources information at the agent level.
This format would effectively extend the following specification:
[http://mesos.apache.org/documentation/attributes-resources/]
{code:title=specification}
kv : text ":" ( range | kvSet | scalar | text )
kvSet : "{" kv ( "," kv )* "}"
info : ( range | text | "*" ) : kvSet
infoSet : "{" info ( "," info )* "}"
resourceName : text | "*"
resourcesInfoValue : text "(" resourceName ")" ":" infoSet
resourcesInfo : resourcesInfoValue ( ";" resourcesInfoValue )*
{code}
{code:javascript|title=example}
--resources= gpus:{card0, card1};ports:[0-100];cpus:8
--resources_info= nvidia(gpus): {
card0: {
uuid: GPU-34e8d7ba-0e4d-ac00-6852-695d5d404f51,
name: GeForce_GTX_980,
path: /dev/nvidia0,
clocks: {
graphic: 1392,
sm: 1392
}
},
card1: {
uuid: GPU-12e457ba-0f4e-bf01-3452-674a5b212c21,
name: GeForce_GTX_970,
path: /dev/nvidia1
clocks: {
graphic: 1392,
sm: 1392
}
},
*: {
driver: 352.39
}
};
services(ports): {
[0-79]: {
type: daemon,
user: root
},
[80-100]: {
type: web_services,
user: www-data
}
};
procs(cpus): {
*: {
name: Intel_i7_6700K,
frequency: 4,
cache: 8
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-3521) Support for hardware topology and resources description
[
https://issues.apache.org/jira/browse/MESOS-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908706#comment-14908706
]
Jonathan Calmels edited comment on MESOS-3521 at 9/25/15 9:39 PM:
--
Well in conjunction with [https://issues.apache.org/jira/browse/MESOS-3366], it
would allow agents to describe their hardware in a well known format. This
format would be standardized, hence schedulers could act upon it to take better
decisions.
Use case scenario:
The agent provides a hook that uses libhwloc and export CPU information (see
the example above). A scheduler could look at the resources_info of each offers
and launch a task on the agent providing the best clock rate.
Following the same logic, we could export GPUs as a custom resource set, and
ask the scheduler to pick say 2 of them that are pairable for a multi-GPU aware
application.
was (Author: exxo):
Well in conjunction with [https://issues.apache.org/jira/browse/MESOS-3366], it
would allow agents to describe their hardware in a well known format. This
format would be standardized, hence schedulers could act upon it to take better
decisions.
Use case scenario:
The agent provides a hook that uses libhwloc and export CPU information (see
the example above). A scheduler could look at the resources_info of each offers
and launch a task on the agent providing the best clock rate.
> Support for hardware topology and resources description
> ---
>
> Key: MESOS-3521
> URL: https://issues.apache.org/jira/browse/MESOS-3521
> Project: Mesos
> Issue Type: Improvement
>Reporter: Jonathan Calmels
>
> In heterogeneous clusters, tasks sometimes have strong constraints on the
> type of hardware they need to execute on. The current solution is to use
> custom attributes to describe resources on the agents.
> While this solution works, the current attribute format is somehow
> constraining and requires workarounds on both the agent and the scheduler
> (e.g. Base64 RFC 6920). In addition, we often need to encode the link between
> an attribute and a resource which is inherently error prone and
> implementation defined from one scheduler to another.
> I would like to propose a unified format to expose hardware topology and
> resources information at the agent level.
> This format would effectively extend the following specification:
> [http://mesos.apache.org/documentation/attributes-resources/]
> {code:title=specification}
> kv : text ":" ( range | kvSet | scalar | text )
> kvSet : "{" kv ( "," kv )* "}"
> info : ( range | text | "*" ) : kvSet
> infoSet : "{" info ( "," info )* "}"
> resourceName : text | "*"
> resourcesInfoValue : text "(" resourceName ")" ":" infoSet
> resourcesInfo : resourcesInfoValue ( ";" resourcesInfoValue )*
> {code}
> {code:javascript|title=example}
> --resources= gpus:{card0, card1};ports:[0-100];cpus:8
> --resources_info= nvidia(gpus): {
> card0: {
> uuid: GPU-34e8d7ba-0e4d-ac00-6852-695d5d404f51,
> name: GeForce_GTX_980,
> path: /dev/nvidia0,
> clocks: {
> graphic: 1392,
> sm: 1392
> }
> },
> card1: {
> uuid: GPU-12e457ba-0f4e-bf01-3452-674a5b212c21,
> name: GeForce_GTX_970,
> path: /dev/nvidia1
> clocks: {
> graphic: 1392,
> sm: 1392
> }
> },
> *: {
> driver: 352.39
> }
>};
>services(ports): {
> [0-79]: {
> type: daemon,
> user: root
> },
> [80-100]: {
> type: web_services,
> user: www-data
> }
>};
>procs(cpus): {
> *: {
> name: Intel_i7_6700K,
> frequency: 4,
> cache: 8
> }
>}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-3519) Fix file descriptor leakage in the code base
Chi Zhang created MESOS-3519: Summary: Fix file descriptor leakage in the code base Key: MESOS-3519 URL: https://issues.apache.org/jira/browse/MESOS-3519 Project: Mesos Issue Type: Bug Reporter: Chi Zhang Assignee: Chi Zhang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3520) Added an abstraction to manage the life cycle of file descriptors
Chi Zhang created MESOS-3520: Summary: Added an abstraction to manage the life cycle of file descriptors Key: MESOS-3520 URL: https://issues.apache.org/jira/browse/MESOS-3520 Project: Mesos Issue Type: Bug Reporter: Chi Zhang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3521) Support for hardware topology and resources description
[
https://issues.apache.org/jira/browse/MESOS-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908668#comment-14908668
]
Vaibhav Khanduja commented on MESOS-3521:
-
[~exxo] Can you please elaborate what could be potential benefits of such
standardization here?
> Support for hardware topology and resources description
> ---
>
> Key: MESOS-3521
> URL: https://issues.apache.org/jira/browse/MESOS-3521
> Project: Mesos
> Issue Type: Improvement
>Reporter: Jonathan Calmels
>
> In heterogeneous clusters, tasks sometimes have strong constraints on the
> type of hardware they need to execute on. The current solution is to use
> custom attributes to describe resources on the agents.
> While this solution works, the current attribute format is somehow
> constraining and requires workarounds on both the agent and the scheduler
> (e.g. Base64 RFC 6920). In addition, we often need to encode the link between
> an attribute and a resource which is inherently error prone and
> implementation defined from one scheduler to another.
> I would like to propose a unified format to expose hardware topology and
> resources information at the agent level.
> This format would effectively extend the following specification:
> [http://mesos.apache.org/documentation/attributes-resources/]
> {code:title=specification}
> kv : text ":" ( range | kvSet | scalar | text )
> kvSet : "{" kv ( "," kv )* "}"
> info : ( range | text | "*" ) : kvSet
> infoSet : "{" info ( "," info )* "}"
> resourceName : text | "*"
> resourcesInfoValue : text "(" resourceName ")" ":" infoSet
> resourcesInfo : resourcesInfoValue ( ";" resourcesInfoValue )*
> {code}
> {code:javascript|title=example}
> --resources= gpus:{card0, card1};ports:[0-100];cpus:8
> --resources_info= nvidia(gpus): {
> card0: {
> uuid: GPU-34e8d7ba-0e4d-ac00-6852-695d5d404f51,
> name: GeForce_GTX_980,
> path: /dev/nvidia0,
> clocks: {
> graphic: 1392,
> sm: 1392
> }
> },
> card1: {
> uuid: GPU-12e457ba-0f4e-bf01-3452-674a5b212c21,
> name: GeForce_GTX_970,
> path: /dev/nvidia1
> clocks: {
> graphic: 1392,
> sm: 1392
> }
> },
> *: {
> driver: 352.39
> }
>};
>services(ports): {
> [0-79]: {
> type: daemon,
> user: root
> },
> [80-100]: {
> type: web_services,
> user: www-data
> }
>};
>procs(cpus): {
> *: {
> name: Intel_i7_6700K,
> frequency: 4,
> cache: 8
> }
>}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3520) Add an abstraction to manage the life cycle of file descriptors
[ https://issues.apache.org/jira/browse/MESOS-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-3520: -- Summary: Add an abstraction to manage the life cycle of file descriptors (was: Added an abstraction to manage the life cycle of file descriptors) > Add an abstraction to manage the life cycle of file descriptors > --- > > Key: MESOS-3520 > URL: https://issues.apache.org/jira/browse/MESOS-3520 > Project: Mesos > Issue Type: Bug >Reporter: Chi Zhang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3521) Support for hardware topology and resources description
[
https://issues.apache.org/jira/browse/MESOS-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908706#comment-14908706
]
Jonathan Calmels commented on MESOS-3521:
-
Well in conjunction with [https://issues.apache.org/jira/browse/MESOS-3366], it
would allow agents to describe their hardware in a well known format. This
format would be standardized, hence schedulers could act upon it to take better
decisions.
Use case scenario:
The agent provides a hook that uses libhwloc and export CPU information (see
the example above). A scheduler could look at the resources_info of each offers
and launch a task on the agent providing the best clock rate.
> Support for hardware topology and resources description
> ---
>
> Key: MESOS-3521
> URL: https://issues.apache.org/jira/browse/MESOS-3521
> Project: Mesos
> Issue Type: Improvement
>Reporter: Jonathan Calmels
>
> In heterogeneous clusters, tasks sometimes have strong constraints on the
> type of hardware they need to execute on. The current solution is to use
> custom attributes to describe resources on the agents.
> While this solution works, the current attribute format is somehow
> constraining and requires workarounds on both the agent and the scheduler
> (e.g. Base64 RFC 6920). In addition, we often need to encode the link between
> an attribute and a resource which is inherently error prone and
> implementation defined from one scheduler to another.
> I would like to propose a unified format to expose hardware topology and
> resources information at the agent level.
> This format would effectively extend the following specification:
> [http://mesos.apache.org/documentation/attributes-resources/]
> {code:title=specification}
> kv : text ":" ( range | kvSet | scalar | text )
> kvSet : "{" kv ( "," kv )* "}"
> info : ( range | text | "*" ) : kvSet
> infoSet : "{" info ( "," info )* "}"
> resourceName : text | "*"
> resourcesInfoValue : text "(" resourceName ")" ":" infoSet
> resourcesInfo : resourcesInfoValue ( ";" resourcesInfoValue )*
> {code}
> {code:javascript|title=example}
> --resources= gpus:{card0, card1};ports:[0-100];cpus:8
> --resources_info= nvidia(gpus): {
> card0: {
> uuid: GPU-34e8d7ba-0e4d-ac00-6852-695d5d404f51,
> name: GeForce_GTX_980,
> path: /dev/nvidia0,
> clocks: {
> graphic: 1392,
> sm: 1392
> }
> },
> card1: {
> uuid: GPU-12e457ba-0f4e-bf01-3452-674a5b212c21,
> name: GeForce_GTX_970,
> path: /dev/nvidia1
> clocks: {
> graphic: 1392,
> sm: 1392
> }
> },
> *: {
> driver: 352.39
> }
>};
>services(ports): {
> [0-79]: {
> type: daemon,
> user: root
> },
> [80-100]: {
> type: web_services,
> user: www-data
> }
>};
>procs(cpus): {
> *: {
> name: Intel_i7_6700K,
> frequency: 4,
> cache: 8
> }
>}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3493) benchmark for declining offers
[ https://issues.apache.org/jira/browse/MESOS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908369#comment-14908369 ] Niklas Quarfot Nielsen commented on MESOS-3493: --- Hey James! Let's get this on a committers radar (and get a shepherd assigned to the issue and reviewers added to your reviews). [~jieyu] [~mcypark] - Would you be up for it? I can help too but think you have more experience in the allocator. Just let me know. > benchmark for declining offers > -- > > Key: MESOS-3493 > URL: https://issues.apache.org/jira/browse/MESOS-3493 > Project: Mesos > Issue Type: Improvement > Components: test >Reporter: James Peach >Priority: Minor > > I wrote a benchmark that can be used to demonstrate the performance issues > addressed in MESOS-3052, MESOS-3051, MESOS-3157 and MESOS-3075. The benchmark > simulates a number of frameworks that start declining all offers once they > reach the limit of work they need to do. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3401) Add labels to Resources
[ https://issues.apache.org/jira/browse/MESOS-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908523#comment-14908523 ] Greg Mann commented on MESOS-3401: -- [~qianzhang], it should be possible to accomplish this using Resource/Attribute arguments as-is, but adding labels may improve the comprehensibility of these structures in cases where there is a lot of fine-grained differentiation between resource-types. i.e. if I have a fairly heterogenous cluster with CPUs of many different speeds, is it desireable to have many different cpu resource names? "cpus2000", "cpus2100", "cpus3000", etc... would require framework authors to parse these resource names in order to distinguish them and recognize them as all members of a particular "class" of resource. Allowing the resource to just be "cpus" improves the user experience from the perspective of the framework author, I think. It also allows the use of the default "cpus" resource name, which may have other benefits? Thoughts? > Add labels to Resources > --- > > Key: MESOS-3401 > URL: https://issues.apache.org/jira/browse/MESOS-3401 > Project: Mesos > Issue Type: Improvement > Components: slave >Reporter: Adam B >Assignee: Greg Mann > Labels: mesosphere, resources > > Similar to how we have added labels to tasks/executors (MESOS-2120), and even > FrameworkInfo (MESOS-2841), we should extend Resource to allow arbitrary > key/value pairs. > This could be used to specify that a cpu resource has a certain speed, that a > disk resource is SSD, or express any other metadata about a built-in or > custom resource type. Only the scalar quantity will be used for determining > fair share in the Mesos allocator. The rest will be passed onto frameworks as > info they can use for scheduling decisions. > This would require changes to how the slave specifies its `--resources` > (probably as json), how the slave/master reports resources in its web/json > API, and how resources are offered to frameworks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3099) Validation of Docker Image Manifests from Docker Registry
[ https://issues.apache.org/jira/browse/MESOS-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-3099: Assignee: Gilbert Song (was: Lily Chen) > Validation of Docker Image Manifests from Docker Registry > - > > Key: MESOS-3099 > URL: https://issues.apache.org/jira/browse/MESOS-3099 > Project: Mesos > Issue Type: Improvement >Reporter: Lily Chen >Assignee: Gilbert Song > Labels: mesosphere > > Docker image manifests pulled from remote Docker registries should be > verified against their signature digest before they are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3428) Support running filesystem isolation with Command Executor in MesosContainerizer
[ https://issues.apache.org/jira/browse/MESOS-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen reassigned MESOS-3428: --- Assignee: Timothy Chen > Support running filesystem isolation with Command Executor in > MesosContainerizer > > > Key: MESOS-3428 > URL: https://issues.apache.org/jira/browse/MESOS-3428 > Project: Mesos > Issue Type: Bug > Components: containerization >Reporter: Timothy Chen >Assignee: Timothy Chen > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3100) Validation of Docker Layers Pulled From Docker Registry
[ https://issues.apache.org/jira/browse/MESOS-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-3100: Assignee: Jojy Varghese (was: Lily Chen) > Validation of Docker Layers Pulled From Docker Registry > --- > > Key: MESOS-3100 > URL: https://issues.apache.org/jira/browse/MESOS-3100 > Project: Mesos > Issue Type: Improvement >Reporter: Lily Chen >Assignee: Jojy Varghese > Labels: mesosphere > > Docker layers should be verified against their checksum digests before they > are stored to ensure the integrity of the docker layer content. This includes > supporting sha256, sha384, sha512 hash algorithms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3493) benchmark for declining offers
[ https://issues.apache.org/jira/browse/MESOS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908447#comment-14908447 ] Joris Van Remoortere commented on MESOS-3493: - I can shepherd this as I helped shepherd some of these patches. > benchmark for declining offers > -- > > Key: MESOS-3493 > URL: https://issues.apache.org/jira/browse/MESOS-3493 > Project: Mesos > Issue Type: Improvement > Components: test >Reporter: James Peach >Priority: Minor > > I wrote a benchmark that can be used to demonstrate the performance issues > addressed in MESOS-3052, MESOS-3051, MESOS-3157 and MESOS-3075. The benchmark > simulates a number of frameworks that start declining all offers once they > reach the limit of work they need to do. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3522) MesosScheduler declineOffer results in an acceptOffer
[ https://issues.apache.org/jira/browse/MESOS-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908842#comment-14908842 ] Vinod Kone commented on MESOS-3522: --- We recently updated the scheduler driver to send Calls instead of old style messages. Please update declineOffers() to send Call::DECLINE instead of using LaunchTasksMessage. > MesosScheduler declineOffer results in an acceptOffer > - > > Key: MESOS-3522 > URL: https://issues.apache.org/jira/browse/MESOS-3522 > Project: Mesos > Issue Type: Bug >Reporter: Jonathan Calmels >Priority: Minor > > Declining an offer through the MesosScheduler results in an empty task being > accepted with no resources. > Extract from the master log: "Processing ACCEPT call for offers ..." > This is due to the implementation of declineOffer which effectively calls > launchTasks with an empty TaskInfo list (sched.cpp:1926) > launchTasks currently emits a Call::ACCEPT, leading to Master::accept > (master.cpp:2634) > Possible fixes include re-implementing declineOffer to emit a Call::DECLINE > or change the launchTasks function to use the LaunchTasksMessage. > I'm not really sure why there are two APIs (messages.proto and > scheduler.proto) to do these tasks so I went with the later. > [https://reviews.apache.org/r/38778/] > Note the TODO would probably duplicate the code from acceptOffers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3522) MesosScheduler declineOffer results in an acceptOffer
Jonathan Calmels created MESOS-3522: --- Summary: MesosScheduler declineOffer results in an acceptOffer Key: MESOS-3522 URL: https://issues.apache.org/jira/browse/MESOS-3522 Project: Mesos Issue Type: Bug Reporter: Jonathan Calmels Priority: Minor Declining an offer through the MesosScheduler results in an empty task being accepted with no resources. Extract from the master log: "Processing ACCEPT call for offers ..." This is due to the implementation of declineOffer which effectively calls launchTasks with an empty TaskInfo list (sched.cpp:1926) launchTasks currently emits a Call::ACCEPT, leading to Master::accept (master.cpp:2634) Possible fixes include re-implementing declineOffer to emit a Call::DECLINE or change the launchTasks function to use the LaunchTasksMessage. I'm not really sure why there are two APIs (messages.proto and scheduler.proto) to do these tasks so I went with the later. Note the TODO would probably duplicate the code from acceptOffers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1615) Create design document for Optimistic Offers
[ https://issues.apache.org/jira/browse/MESOS-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908870#comment-14908870 ] Joseph Wu commented on MESOS-1615: -- [~bmahler], Is it ok if we (Mesosphere/IBM working group on optimistic offers) take over this ticket? > Create design document for Optimistic Offers > > > Key: MESOS-1615 > URL: https://issues.apache.org/jira/browse/MESOS-1615 > Project: Mesos > Issue Type: Documentation >Reporter: Dominic Hamon >Assignee: Benjamin Mahler > > As a first step toward Optimistic Offers, take the description from the epic > and build an implementation design doc that can be shared for comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3523) Teach cpplint to catch more coding style issues
Cong Wang created MESOS-3523:
Summary: Teach cpplint to catch more coding style issues
Key: MESOS-3523
URL: https://issues.apache.org/jira/browse/MESOS-3523
Project: Mesos
Issue Type: Bug
Reporter: Cong Wang
Our current cpplint hook can't catch the following coding style issues:
1. Two blank lines before public/private/protect, for example:
{noformat}
class foo{
public:
foo();
private:
int bar;
protect:
int biz;
};
{noformat}
2. Braces not in the same line when the definition is empty, for example,
{noformat}
class Foo {
private:
Foo()
{}
};
{noformat}
3. Comment line longer than 70 characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3523) Teach cpplint to catch more coding style issues
[
https://issues.apache.org/jira/browse/MESOS-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cong Wang updated MESOS-3523:
-
Issue Type: Improvement (was: Bug)
> Teach cpplint to catch more coding style issues
> ---
>
> Key: MESOS-3523
> URL: https://issues.apache.org/jira/browse/MESOS-3523
> Project: Mesos
> Issue Type: Improvement
>Reporter: Cong Wang
>
> Our current cpplint hook can't catch the following coding style issues:
> 1. Two blank lines before public/private/protect, for example:
> {noformat}
> class foo{
> public:
> foo();
> private:
> int bar;
> protect:
> int biz;
> };
> {noformat}
> 2. Braces not in the same line when the definition is empty, for example,
> {noformat}
> class Foo {
> private:
> Foo()
> {}
> };
> {noformat}
> 3. Comment line longer than 70 characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3523) Teach cpplint to catch more coding style issues
[
https://issues.apache.org/jira/browse/MESOS-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cong Wang updated MESOS-3523:
-
Description:
Our current cpplint hook can't catch the following coding style issues:
1. Two blank lines before public/private/protect, for example:
{noformat}
class foo{
public:
foo();
private:
int bar;
protect:
int biz;
};
{noformat}
2. Braces not in the same line when the definition is empty, for example,
{noformat}
class Foo {
private:
Foo()
{}
};
{noformat}
3. Comment line longer than 70 characters.
4. Initialization lists indention, for example
{noformat}
class Foo
{
Foo()
: bar(_bar)
{}
};
{noformat}
was:
Our current cpplint hook can't catch the following coding style issues:
1. Two blank lines before public/private/protect, for example:
{noformat}
class foo{
public:
foo();
private:
int bar;
protect:
int biz;
};
{noformat}
2. Braces not in the same line when the definition is empty, for example,
{noformat}
class Foo {
private:
Foo()
{}
};
{noformat}
3. Comment line longer than 70 characters.
> Teach cpplint to catch more coding style issues
> ---
>
> Key: MESOS-3523
> URL: https://issues.apache.org/jira/browse/MESOS-3523
> Project: Mesos
> Issue Type: Improvement
>Reporter: Cong Wang
>
> Our current cpplint hook can't catch the following coding style issues:
> 1. Two blank lines before public/private/protect, for example:
> {noformat}
> class foo{
> public:
> foo();
> private:
> int bar;
> protect:
> int biz;
> };
> {noformat}
> 2. Braces not in the same line when the definition is empty, for example,
> {noformat}
> class Foo {
> private:
> Foo()
> {}
> };
> {noformat}
> 3. Comment line longer than 70 characters.
> 4. Initialization lists indention, for example
> {noformat}
> class Foo
> {
> Foo()
> : bar(_bar)
> {}
> };
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2863) Command executor can send TASK_KILLED after TASK_FINISHED
[ https://issues.apache.org/jira/browse/MESOS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908915#comment-14908915 ] Vaibhav Khanduja commented on MESOS-2863: - [~vinodkone]Looks like I can resolve this a not reproducible? > Command executor can send TASK_KILLED after TASK_FINISHED > - > > Key: MESOS-2863 > URL: https://issues.apache.org/jira/browse/MESOS-2863 > Project: Mesos > Issue Type: Bug >Reporter: Vinod Kone >Assignee: Vaibhav Khanduja > Labels: newbie++ > > Observed this while doing some tests in our test cluster. > If the command executor gets a shutdown() (e.g., framework unregistered) > after sending TASK_FINISHED but before exiting (there is a forced sleep), it > could send a TASK_KILLED update to the slave. > Ideally the command executor should not send multiple terminal updates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2035) Add reason to containerizer proto Termination
[ https://issues.apache.org/jira/browse/MESOS-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908917#comment-14908917 ] Jie Yu commented on MESOS-2035: --- Summary of the current semantics and proposed a new semantics in the following doc: https://docs.google.com/document/d/1klGDAu5yBVf-CGWLqvELLIfxLfRaisGkhi6Gn7952-4/edit?usp=sharing > Add reason to containerizer proto Termination > - > > Key: MESOS-2035 > URL: https://issues.apache.org/jira/browse/MESOS-2035 > Project: Mesos > Issue Type: Improvement > Components: slave >Affects Versions: 0.21.0 >Reporter: Dominic Hamon >Assignee: Jie Yu > Labels: mesosphere > > When an isolator kills a task, the reason is unknown. As part of MESOS-1830, > the reason is set to a general one but ideally we would have the termination > reason to pass through to the status update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3524) HTTP API v1 Protobuf Jar in maven central
Ben Whitehead created MESOS-3524: Summary: HTTP API v1 Protobuf Jar in maven central Key: MESOS-3524 URL: https://issues.apache.org/jira/browse/MESOS-3524 Project: Mesos Issue Type: Story Components: HTTP API Affects Versions: 0.24.0, 0.25.0 Reporter: Ben Whitehead Priority: Critical As a developer working on the JVM I would like mesos to provide a JAR containing the new protobuf classes for the HTTP API. Please create a new jar that contains the Protobuf message file and generated java and class files generated from the message file. This jar should be published to maven central. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3524) HTTP API v1 Protobuf Jar in maven central
[ https://issues.apache.org/jira/browse/MESOS-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908934#comment-14908934 ] Vinod Kone commented on MESOS-3524: --- We are planning to move the project away from officially supporting anything other than C++. As such, we need to discuss if we should be responsible for uploading protobuf classes to language specific distribution channels (maven, pypi etc). > HTTP API v1 Protobuf Jar in maven central > - > > Key: MESOS-3524 > URL: https://issues.apache.org/jira/browse/MESOS-3524 > Project: Mesos > Issue Type: Story > Components: HTTP API >Affects Versions: 0.24.0, 0.25.0 >Reporter: Ben Whitehead >Priority: Critical > Labels: http, jar, java, maven, protobuf > > As a developer working on the JVM I would like mesos to provide a JAR > containing the new protobuf classes for the HTTP API. > Please create a new jar that contains the Protobuf message file and generated > java and class files generated from the message file. This jar should be > published to maven central. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3525) Figure out how to enforce 64-bit builds on Windows.
Alex Clemmer created MESOS-3525: --- Summary: Figure out how to enforce 64-bit builds on Windows. Key: MESOS-3525 URL: https://issues.apache.org/jira/browse/MESOS-3525 Project: Mesos Issue Type: Task Components: build Reporter: Alex Clemmer Assignee: Alex Clemmer We need to make sure people don't try to compile Mesos on 32-bit architectures. We don't want a Windows repeat of something like this: https://issues.apache.org/jira/browse/MESOS-267 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3507) As an operator, I want a way to inspect queued tasks in running schedulers
[ https://issues.apache.org/jira/browse/MESOS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14909004#comment-14909004 ] James DeFelice commented on MESOS-3507: --- I like the idea of frameworks publishing multiple urls. Perhaps labeled. Maybe an endpoint message that consists of a name and a url. Possibly add acl or visibility later. Frameworks could publish multiple endpoints. This would be great for kubernetes. > As an operator, I want a way to inspect queued tasks in running schedulers > -- > > Key: MESOS-3507 > URL: https://issues.apache.org/jira/browse/MESOS-3507 > Project: Mesos > Issue Type: Story >Reporter: Niklas Quarfot Nielsen > > Currently, there is no uniform way of getting a notion of 'awaiting' tasks > i.e. expressing that a framework has more work to do. This information is > useful for auto-scaling and anomaly detection systems. Schedulers tend to > expose this over their own http endpoints, but the format across schedulers > are most likely not compatible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2376) Allow libprocess ip and port to be configured
[ https://issues.apache.org/jira/browse/MESOS-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907724#comment-14907724 ] Matthias Veit commented on MESOS-2376: -- [~timchen] So how can we control this value without using the env vars? In Marathon we are setting the FrameworkInfo.hostName, since this is the hostName resolved by the system or given by the user from the command line and would be the best option to use. But it looks like this value does not impact LIBPROCESS_IP. > Allow libprocess ip and port to be configured > - > > Key: MESOS-2376 > URL: https://issues.apache.org/jira/browse/MESOS-2376 > Project: Mesos > Issue Type: Improvement > Components: java api >Reporter: Dario Rexin >Priority: Minor > > Currently if we want to configure the ip libprocess uses for communication, > we have to set the env var LIBPROCESS_IP, or LIBPROCESS_PORT for the port. > For the Java API this means, that the variable has to be set before the JVM > is started, because setting env vars from within JAVA is not possible / > non-trivial. Therefore it would be great to be able to pass them in to the > constructor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: [root@chenqiang-master-dev001-shgq ~]# telnet 127.0.0.1 5050
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: You could open http://:5050 successfully in other machine?)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: Could you "curl http://127.0.0.1:5050/help; success? And also use netstat
to make sure mesos-master is listened on 5050.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: It's there some good idea to fix the my connection issue? thanks.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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,
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: It returned with nothing...
What' state json playload should be got? thanks.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 ]
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: [root@chenqiang-master-dev001-shgq ~]# curl http://127.0.0.1:5050/help -i
HTTP/1.1 200 OK
Date: Mon, 21 Sep 2015 12:14:15 GMT
Content-Type: text/x-markdown
Content-Length: 409
## HELP
> [/__processes__][__processes__]
> [/files][files]
> [/logging][logging]
> [/master][master]
> [/metrics][metrics]
> [/profiler][profiler]
> [/registrar(1)][registrar(1)]
> [/system][system]
[__processes__]: help/__processes__
[files]: help/files
[logging]: help/logging
[master]: help/master
[metrics]: help/metrics
[profiler]: help/profiler
[registrar(1)]: help/registrar(1)
[system]: help/system
[root@chenqiang-master-dev001-shgq ~]# netstat -tlanp | grep 5050
tcp0 0 127.0.0.1:5050 0.0.0.0:*
LISTEN 4289/lt-mesos-maste
tcp0 0 127.0.0.1:5050 127.0.0.1:40460
ESTABLISHED 4289/lt-mesos-maste
tcp0 0 127.0.0.1:40460 127.0.0.1:5050
ESTABLISHED 4315/lt-mesos-slave
)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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,
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: You aslo could curl http://127.0.0.1:5050/maste/state.json successfully?)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 ]
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: of course not, you started mesos-master with specified ip 127.0.0.1,
which is a local loop back address.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 ]
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: good leader)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: selinux also closed.
[root@chenqiang-master-dev001-shgq yum.repos.d]# setenforce 0
[root@chenqiang-master-dev001-shgq yum.repos.d]# getenforce
Permissive
)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: Generally, the local loop back IP will redirect to its ethernet IP, so we
can use the ethernet IP to access. So I specify the ethx IP directly which
works finally. I encountered that when I start the gitbook sever by
127.0.0.1:4000, it would be connected with its Ethx IP when we from Windows or
other linux systems.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 ]
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: The issue is fixed by instead of local loopback ip 127.0.0.1 with
ex.
$ ./bin/mesos-master.sh --ip=10.210.175.16 --work_dir=/var/lib/mesos)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: yes, I thought it would be related to these, but I found not later. So, I
commened to expain that before, OK, thanks all you guys. )
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: Yes, and I guess this problem is not relate to mesos, maybe related to
your server configuration. And I suggest use
{code}
$ netstat -antp|grep 5050
{code}
and
{code}
$ python -m SimpleHTTPServer 5050
{code}
to find which part is wrong first.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: OK, it means those are not the root cause that made me can't access to
http:127.0.0.1:5050)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 ]
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: this is generally a beginning question, irrelative with this issue,
mesos-user mailing list is the good place to go. :-))
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: Which version are you used? master branch or 0.24? And what is your
operation system?)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 ]
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[ https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Massenzio updated MESOS-3079: --- Comment: was deleted (was: my fails listed below, thanks. [==] 713 tests from 117 test cases ran. (301085 ms total) [ PASSED ] 676 tests. [ FAILED ] 37 tests, listed below: [ FAILED ] PerfTest.ROOT_SamplePid [ FAILED ] CgroupsNoHierarchyTest.ROOT_CGROUPS_NOHIERARCHY_MountUnmountHierarchy [ FAILED ] CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf [ FAILED ] CgroupsAnyHierarchyMemoryPressureTest.ROOT_IncreaseUnlockedRSS [ FAILED ] CgroupsAnyHierarchyMemoryPressureTest.ROOT_IncreasePageCache [ 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 ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample [ FAILED ] UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup, where TypeParam = mesos::internal::slave::CgroupsMemIsolatorProcess [ FAILED ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup, where TypeParam = mesos::internal::slave::CgroupsCpushareIsolatorProcess [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess 37 FAILED TESTS YOU HAVE 12 DISABLED TESTS I0921 14:01:07.216980 29337 exec.cpp:452] Slave exited, but framework has checkpointing enabled. Waiting 15mins to reconnect with slave 20150921-135826-2186009866-44268-27222-S0 make[3]: *** [check-local] Error 1 make[3]: Leaving directory `/home/chenqiang/downloads/mesos-0.23.0/build/src' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/home/chenqiang/downloads/mesos-0.23.0/build/src' make[1]: *** [check] Error 2 make[1]: Leaving directory `/home/chenqiang/downloads/mesos-0.23.0/build/src' make: *** [check-recursive] Error 1 ) > `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too) >
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: Hi haosdent,
Thanks for your quick response.
I use the centos 6.4 x86_64, mesos0.23.0, g++ 4.8.1
I checked that the 5050 port is in listen and establish status.
-
In mesos-master side, I saw following msg:
I0921 16:31:26.478057 4309 hierarchical.hpp:588] Slave
20150921-130346-16777343-5050-23074-S0 (my-vm) updated with oversubscribed
resources (total: cpus(*):4; mem(*):6845; disk(*):31036;
ports(*):[31000-32000], allocated: )
and in mesos-slave side,
I0921 16:59:11.596024 4340 slave.cpp:4179] Querying resource estimator for
oversubscribable resources
I0921 16:59:11.596247 4340 slave.cpp:4193] Received oversubscribable resources
from the resource estimator
Thanks.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: Hi Marco Massenzio, I encountered those 37 fails also, and I run
following commands, I can't connect to the mesos web page via
http://127.0.0.1:5050, so does those failures made it cannot access or still
have others? thanks.
# Start mesos master (Ensure work directory exists and has proper
permissions).
$ ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos
# Start mesos slave.
$ ./bin/mesos-slave.sh --master=127.0.0.1:5050
# Visit the mesos web page.
$ http://127.0.0.1:5050)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: no, can't too.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: You could ignore this failed tests.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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 =
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3079:
---
Comment: was deleted
(was: Could you telnet to 127.0.0.1 5050 in mesos master machine?)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ 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
[jira] [Commented] (MESOS-1478) Replace Master/Slave terminology
[ https://issues.apache.org/jira/browse/MESOS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907989#comment-14907989 ] Johannes Ziemke commented on MESOS-1478: Any update on this? I would propose calling them coordinator and agent where a coordinator can be leader or follower. That's even more specific than what we have right now. > Replace Master/Slave terminology > > > Key: MESOS-1478 > URL: https://issues.apache.org/jira/browse/MESOS-1478 > Project: Mesos > Issue Type: Wish >Reporter: Clark Breyman >Assignee: Benjamin Hindman >Priority: Minor > Labels: mesosphere > > Inspired by the comments on this PR: > https://github.com/django/django/pull/2692 > TL;DR - Computers sharing work should be a good thing. Using the language of > human bondage and suffering is inappropriate in this context. It also has the > potential to alienate users and community members. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3517) Building mesos from source fails when OS language is not English
Wessel Nieboer created MESOS-3517: - Summary: Building mesos from source fails when OS language is not English Key: MESOS-3517 URL: https://issues.apache.org/jira/browse/MESOS-3517 Project: Mesos Issue Type: Bug Components: build Environment: Dutch locale on Ubuntu 15.04 Reporter: Wessel Nieboer Priority: Minor Line 963 of mesos/3rdparty/libprocess/3rdparty/stout/tests/os_tests.cpp contains the following: EXPECT_TRUE(strings::contains(result.get(), "No such file or directory")); But this does not match when your locale is not English. When changing it to what my terminal gives me: "Bestand of map bestaat niet" then it works just fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3518) Assertions that compare doubles with == can fail due to rounding issues and can crash the master.
Max Neunhöffer created MESOS-3518: - Summary: Assertions that compare doubles with == can fail due to rounding issues and can crash the master. Key: MESOS-3518 URL: https://issues.apache.org/jira/browse/MESOS-3518 Project: Mesos Issue Type: Bug Components: master Affects Versions: 0.24.1, 0.24.0, 0.23.1, 0.23.0 Reporter: Max Neunhöffer Priority: Minor mesos-0.23.0/src/common/resources.cpp has CHECK(result.cpus() == cpus() && result.mem() == mem() && result.disk() == disk() && result.ports() == ports()); at around line 869. Sometimes, rounding errors can trigger this check to fail because of the cpus() part. One should take the absolute value of the difference and compare with a small value to avoid this problem. The same problem could be true in various places, so far I have not yet checked. Seems to be present in all versions I checked. I could trigger this by asking for some resource value of cpus(*):0.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
