[jira] [Created] (MESOS-1624) Apache Jenkins build fails due to -lsnappy is set when building leveldb
Yan Xu created MESOS-1624:
-
Summary: Apache Jenkins build fails due to -lsnappy is set when
building leveldb
Key: MESOS-1624
URL: https://issues.apache.org/jira/browse/MESOS-1624
Project: Mesos
Issue Type: Bug
Components: build
Environment: ubuntu, more here:
https://builds.apache.org/computer/ubuntu-2/systemInfo
Reporter: Yan Xu
The failed build:
https://builds.apache.org/job/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/2261/consoleFull
{noformat:title=the log where -lsnappy is used when compiling leveldb}
gzip -d -c ../../3rdparty/leveldb.tar.gz | tar xf -
test ! -e ../../3rdparty/leveldb.patch || patch -d leveldb -p1
<../../3rdparty/leveldb.patch
touch leveldb-stamp
cd leveldb && \
make CC="gcc" CXX="g++" OPT="-g -g2 -O2 -Wno-unused-local-typedefs
-std=c++11 -fPIC"
make[5]: Entering directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/mesos-0.20.0/_build/3rdparty/leveldb'
g++ -pthread -lsnappy -shared -Wl,-soname
-Wl,/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/mesos-0.20.0/_build/3rdparty/leveldb/libleveldb.so.1
-I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX
-DLEVELDB_PLATFORM_POSIX -DSNAPPY -g -g2 -O2 -Wno-unused-local-typedefs
-std=c++11 -fPIC -fPIC db/builder.cc db/c.cc db/db_impl.cc db/db_iter.cc
db/dbformat.cc db/filename.cc db/log_reader.cc db/log_writer.cc db/memtable.cc
db/repair.cc db/table_cache.cc db/version_edit.cc db/version_set.cc
db/write_batch.cc table/block.cc table/block_builder.cc table/filter_block.cc
table/format.cc table/iterator.cc table/merger.cc table/table.cc
table/table_builder.cc table/two_level_iterator.cc util/arena.cc util/bloom.cc
util/cache.cc util/coding.cc util/comparator.cc util/crc32c.cc util/env.cc
util/env_posix.cc util/filter_policy.cc util/hash.cc util/histogram.cc
util/logging.cc util/options.cc util/status.cc port/port_posix.cc -o
libleveldb.so.1.4
ln -fs libleveldb.so.1.4 libleveldb.so
ln -fs libleveldb.so.1.4 libleveldb.so.1
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX
-DLEVELDB_PLATFORM_POSIX -DSNAPPY -g -g2 -O2 -Wno-unused-local-typedefs
-std=c++11 -fPIC -c db/builder.cc -o db/builder.o
{noformat}
{noformat:title=the error}
/bin/bash ../libtool --tag=CXX --mode=link g++ -pthread -g -g2 -O2
-Wno-unused-local-typedefs -std=c++11 -o mesos-local local/mesos_local-main.o
libmesos.la -lsasl2 -lcurl -lz -lrt
libtool: link: g++ -pthread -g -g2 -O2 -Wno-unused-local-typedefs -std=c++11 -o
.libs/mesos-local local/mesos_local-main.o ./.libs/libmesos.so -lsasl2
/usr/lib/x86_64-linux-gnu/libcurl.so -lz -lrt -pthread -Wl,-rpath
-Wl,/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/mesos-0.20.0/_inst/lib
./.libs/libmesos.so: undefined reference to `snappy::RawCompress(char const*,
unsigned long, char*, unsigned long*)'
./.libs/libmesos.so: undefined reference to `snappy::RawUncompress(char const*,
unsigned long, char*)'
./.libs/libmesos.so: undefined reference to `snappy::GetUncompressedLength(char
const*, unsigned long, unsigned long*)'
./.libs/libmesos.so: undefined reference to
`snappy::MaxCompressedLength(unsigned long)'
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (MESOS-1621) Docker run networking should be configurable
[ https://issues.apache.org/jira/browse/MESOS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069797#comment-14069797 ] Timothy Chen commented on MESOS-1621: - When you mention an args override, you're mentioning an override to provide any docker options, not just network? > Docker run networking should be configurable > > > Key: MESOS-1621 > URL: https://issues.apache.org/jira/browse/MESOS-1621 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen > Labels: Docker > > Currently to easily support running executors in Docker image, we hardcode > --net=host into Docker run so slave and executor and reuse the same mechanism > to communicate, which is to pass the slave IP/PORT for the framework to > respond with it's own hostname and port information back to setup the tunnel. > We want to see how to abstract this or even get rid of host networking > altogether if we have a good way to not rely on it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1622) Move implementations from .hpp to .cpp
[ https://issues.apache.org/jira/browse/MESOS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-1622: -- Description: This issue is related to MESOS-1582, some headers have unnecessary inline definitions and function declarations, to speed up build time we are lightening headers. This issue will not apply to stout. > Move implementations from .hpp to .cpp > -- > > Key: MESOS-1622 > URL: https://issues.apache.org/jira/browse/MESOS-1622 > Project: Mesos > Issue Type: Improvement >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > > This issue is related to MESOS-1582, some headers have unnecessary inline > definitions and function declarations, to speed up build time we are > lightening headers. This issue will not apply to stout. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1622) Move implementations from .hpp to .cpp
[ https://issues.apache.org/jira/browse/MESOS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069616#comment-14069616 ] Timothy St. Clair commented on MESOS-1622: -- Description? > Move implementations from .hpp to .cpp > -- > > Key: MESOS-1622 > URL: https://issues.apache.org/jira/browse/MESOS-1622 > Project: Mesos > Issue Type: Improvement >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (MESOS-987) Wire up a code coverage tool
[
https://issues.apache.org/jira/browse/MESOS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069254#comment-14069254
]
Dominic Hamon edited comment on MESOS-987 at 7/21/14 11:38 PM:
---
An alternative to adding it to the configure script:
{noformat}
$ CXXFLAGS="-pg --coverage" LDFLAGS=-lgcov ./configure
$ make check GTEST_FILTER='*'
$ cd build/src
$ find -name \*.gcno | xargs gcov
...
Lines executed:64.46% of 6
$ lcov --directory . -c -o report.info --ignore-errors source
$ genhtml report.info --output-directory /tmp/lcov
$ Overall coverage rate:
lines..: 64.5% (44364 of 68821 lines)
functions..: 47.6% (28304 of 59445 functions)
{noformat}
Though this doesn't exclude 3rdparty and system folders.
was (Author: dhamon):
An alternative to adding it to the configure script:
{noformat}
$ CXXFLAGS="-pg --coverage" LDFLAGS=-lgcov ./configure
$ make check GTEST_FILTER=''
$ cd build/src && ./mesos-tests
$ find -name \*.gcno | xargs gcov
...
Lines executed:64.46% of 6
$
{noformat}
> Wire up a code coverage tool
>
>
> Key: MESOS-987
> URL: https://issues.apache.org/jira/browse/MESOS-987
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt
>Reporter: Vinod Kone
>Assignee: Dominic Hamon
>
> Some options are gcov (works only with gcc afaict) and optionally lcov.
> It would be nice to hook this up with Jenkins too.
> http://meekrosoft.wordpress.com/2010/06/02/continuous-code-coverage-with-gcc-googletest-and-hudson/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (MESOS-1622) Move implementations from .hpp to .cpp
[ https://issues.apache.org/jira/browse/MESOS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez reassigned MESOS-1622: - Assignee: Isabel Jimenez > Move implementations from .hpp to .cpp > -- > > Key: MESOS-1622 > URL: https://issues.apache.org/jira/browse/MESOS-1622 > Project: Mesos > Issue Type: Improvement >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1623) Separate large .cpp
[ https://issues.apache.org/jira/browse/MESOS-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-1623: -- Attachment: compile.csv > Separate large .cpp > --- > > Key: MESOS-1623 > URL: https://issues.apache.org/jira/browse/MESOS-1623 > Project: Mesos > Issue Type: Improvement >Reporter: Isabel Jimenez > Attachments: compile.csv > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1623) Separate large .cpp
[ https://issues.apache.org/jira/browse/MESOS-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069447#comment-14069447 ] Isabel Jimenez commented on MESOS-1623: --- Attaching csv file with build time logs for .cpp files. This way, we can start by the slowest. > Separate large .cpp > --- > > Key: MESOS-1623 > URL: https://issues.apache.org/jira/browse/MESOS-1623 > Project: Mesos > Issue Type: Improvement >Reporter: Isabel Jimenez > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1622) Move implementations from .hpp to .cpp
[ https://issues.apache.org/jira/browse/MESOS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069432#comment-14069432 ] Isabel Jimenez commented on MESOS-1622: --- https://reviews.apache.org/r/23745/ > Move implementations from .hpp to .cpp > -- > > Key: MESOS-1622 > URL: https://issues.apache.org/jira/browse/MESOS-1622 > Project: Mesos > Issue Type: Improvement >Reporter: Isabel Jimenez > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1623) Separate large .cpp
Isabel Jimenez created MESOS-1623: - Summary: Separate large .cpp Key: MESOS-1623 URL: https://issues.apache.org/jira/browse/MESOS-1623 Project: Mesos Issue Type: Improvement Reporter: Isabel Jimenez -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1622) Move implementations from .hpp to .cpp
Isabel Jimenez created MESOS-1622: - Summary: Move implementations from .hpp to .cpp Key: MESOS-1622 URL: https://issues.apache.org/jira/browse/MESOS-1622 Project: Mesos Issue Type: Improvement Reporter: Isabel Jimenez -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1621) Docker run networking should be configurable
[ https://issues.apache.org/jira/browse/MESOS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy St. Clair updated MESOS-1621: - Labels: Docker (was: docker) > Docker run networking should be configurable > > > Key: MESOS-1621 > URL: https://issues.apache.org/jira/browse/MESOS-1621 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen > Labels: Docker > > Currently to easily support running executors in Docker image, we hardcode > --net=host into Docker run so slave and executor and reuse the same mechanism > to communicate, which is to pass the slave IP/PORT for the framework to > respond with it's own hostname and port information back to setup the tunnel. > We want to see how to abstract this or even get rid of host networking > altogether if we have a good way to not rely on it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (MESOS-1621) Docker run networking should be configurable
[ https://issues.apache.org/jira/browse/MESOS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069251#comment-14069251 ] Timothy St. Clair edited comment on MESOS-1621 at 7/21/14 8:58 PM: --- Here is a state space: https://github.com/GoogleCloudPlatform/kubernetes/issues/494 Here is my hope for the future: https://groups.google.com/forum/#!topic/docker-dev/6tt1y9FTWKg Either way, we need to enable an args override. was (Author: tstclair): Here is a state space: GoogleCloudPlatform/kubernetes#494 Here is my hope for the future: https://groups.google.com/forum/#!topic/docker-dev/6tt1y9FTWKg Either way, we need to enable an args override. > Docker run networking should be configurable > > > Key: MESOS-1621 > URL: https://issues.apache.org/jira/browse/MESOS-1621 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen > Labels: docker > > Currently to easily support running executors in Docker image, we hardcode > --net=host into Docker run so slave and executor and reuse the same mechanism > to communicate, which is to pass the slave IP/PORT for the framework to > respond with it's own hostname and port information back to setup the tunnel. > We want to see how to abstract this or even get rid of host networking > altogether if we have a good way to not rely on it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-987) Wire up a code coverage tool
[
https://issues.apache.org/jira/browse/MESOS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069254#comment-14069254
]
Dominic Hamon commented on MESOS-987:
-
An alternative to adding it to the configure script:
{noformat}
$ CXXFLAGS="-pg --coverage" LDFLAGS=-lgcov ./configure
$ make check GTEST_FILTER=''
$ cd build/src && ./mesos-tests
$ find -name \*.gcno | xargs gcov
...
Lines executed:64.46% of 6
$
{noformat}
> Wire up a code coverage tool
>
>
> Key: MESOS-987
> URL: https://issues.apache.org/jira/browse/MESOS-987
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt
>Reporter: Vinod Kone
>Assignee: Dominic Hamon
>
> Some options are gcov (works only with gcc afaict) and optionally lcov.
> It would be nice to hook this up with Jenkins too.
> http://meekrosoft.wordpress.com/2010/06/02/continuous-code-coverage-with-gcc-googletest-and-hudson/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (MESOS-1621) Docker run networking should be configurable
[ https://issues.apache.org/jira/browse/MESOS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069251#comment-14069251 ] Timothy St. Clair commented on MESOS-1621: -- Here is a state space: GoogleCloudPlatform/kubernetes#494 Here is my hope for the future: https://groups.google.com/forum/#!topic/docker-dev/6tt1y9FTWKg Either way, we need to enable an args override. > Docker run networking should be configurable > > > Key: MESOS-1621 > URL: https://issues.apache.org/jira/browse/MESOS-1621 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen > Labels: docker > > Currently to easily support running executors in Docker image, we hardcode > --net=host into Docker run so slave and executor and reuse the same mechanism > to communicate, which is to pass the slave IP/PORT for the framework to > respond with it's own hostname and port information back to setup the tunnel. > We want to see how to abstract this or even get rid of host networking > altogether if we have a good way to not rely on it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1619) OsTest.User test is flaky
[
https://issues.apache.org/jira/browse/MESOS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069234#comment-14069234
]
Ian Downes commented on MESOS-1619:
---
Host appears okay.
Reading man getpwnam_r it's not clear to me why ENOENT together with non-zero
return code is being returned.
{noformat}
On success, getpwnam_r() and getpwuid_r() return zero, and set *result to pwd.
If no matching password record was found, these functions return 0 and store
NULL in *result. In case of error, an error number is returned, and NULL is
stored in *result.
{noformat}
But, later it states it can set ENOENT, which isn't part of the Posix
specification as far as I can tell.
{noformat}
ERRORS
0 or ENOENT or ESRCH or EBADF or EPERM or ...
The given name or uid was not found.
{noformat}
> OsTest.User test is flaky
> -
>
> Key: MESOS-1619
> URL: https://issues.apache.org/jira/browse/MESOS-1619
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: centos7 w/ gcc
>Reporter: Vinod Kone
>
> [ RUN ] OsTest.user
> stout/tests/os_tests.cpp:720: Failure
> Value of: os::getuid(UUID::random().toString()).isNone()
> Actual: false
> Expected: true
> stout/tests/os_tests.cpp:721: Failure
> Value of: os::getgid(UUID::random().toString()).isNone()
> Actual: false
> Expected: true
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> E0721 06:15:58.656255 13440 os.hpp:731] Failed to set gid: Failed to get
> username information: No such file or directory
> [ FAILED ] OsTest.user (20 ms)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (MESOS-1621) Docker run networking should be configurable
Timothy Chen created MESOS-1621: --- Summary: Docker run networking should be configurable Key: MESOS-1621 URL: https://issues.apache.org/jira/browse/MESOS-1621 Project: Mesos Issue Type: Improvement Reporter: Timothy Chen Currently to easily support running executors in Docker image, we hardcode --net=host into Docker run so slave and executor and reuse the same mechanism to communicate, which is to pass the slave IP/PORT for the framework to respond with it's own hostname and port information back to setup the tunnel. We want to see how to abstract this or even get rid of host networking altogether if we have a good way to not rely on it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1593) Add DockerInfo Configuration
[ https://issues.apache.org/jira/browse/MESOS-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069229#comment-14069229 ] Timothy Chen commented on MESOS-1593: - [~gabrtv] For Pods co-located features we're very early beginning to think about what it might look like, so your feedback will be very valuable, as well as the Docker linking. The ambassador pattern is just a note seeing how most Docker users solve the same problem, but not necessarily something we'll incorporate yet. I believe our first iteration on DockerInfo will most likely not support it as it is very evolving as you said. > Add DockerInfo Configuration > > > Key: MESOS-1593 > URL: https://issues.apache.org/jira/browse/MESOS-1593 > Project: Mesos > Issue Type: Task >Reporter: Timothy Chen >Assignee: Timothy Chen > > We want to add a new proto message to encapsulate all Docker related > configurations into DockerInfo. > Here is the document that describes the design for DockerInfo: > https://github.com/tnachen/mesos/wiki/DockerInfo-design -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1593) Add DockerInfo Configuration
[
https://issues.apache.org/jira/browse/MESOS-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069223#comment-14069223
]
Timothy Chen commented on MESOS-1593:
-
[~gabrtv] Let me respond to your comments in several pieces, but let me answer
few points you have:
We currently are using the docker name to record some metadata about the docker
running instance, which all mesos launched docker instances have names format
as "mesos-#{containerID}"
--ports is something to consider, will be curious what variations you like to
see supported and how that looks like in DockerInfo
(https://docs.docker.com/reference/run/#expose-incoming-ports)
DockerInfo will be supporting the standard Environment message as in
CommandInfo, and what you provide there will be passed in to docker run exactly
with -e flag. Our current code actually already supports this too, you just
need to provide Env variables in CommandInfo.
Docker auto rm/kill is supported already, and it follows the Mesos executor
lifecycle. Once a task is killed we automatically kill and rm the container for
you. In slave recovery we also reap the dangling docker containers that is not
checkpointed as well, so there shouldn't be any left running docker images.
> Add DockerInfo Configuration
>
>
> Key: MESOS-1593
> URL: https://issues.apache.org/jira/browse/MESOS-1593
> Project: Mesos
> Issue Type: Task
>Reporter: Timothy Chen
>Assignee: Timothy Chen
>
> We want to add a new proto message to encapsulate all Docker related
> configurations into DockerInfo.
> Here is the document that describes the design for DockerInfo:
> https://github.com/tnachen/mesos/wiki/DockerInfo-design
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Closed] (MESOS-1583) Clang tool build improvement "include what you use"
[ https://issues.apache.org/jira/browse/MESOS-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez closed MESOS-1583. - Resolution: Fixed > Clang tool build improvement "include what you use" > --- > > Key: MESOS-1583 > URL: https://issues.apache.org/jira/browse/MESOS-1583 > Project: Mesos > Issue Type: Improvement > Components: technical debt >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > Attachments: Screen Shot 2014-07-16 at 11.56.01 AM.png > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (MESOS-1583) Clang tool build improvement "include what you use"
[ https://issues.apache.org/jira/browse/MESOS-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-1583: -- Comment: was deleted (was: IWYU screenshot ) > Clang tool build improvement "include what you use" > --- > > Key: MESOS-1583 > URL: https://issues.apache.org/jira/browse/MESOS-1583 > Project: Mesos > Issue Type: Improvement > Components: technical debt >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > Attachments: Screen Shot 2014-07-16 at 11.56.01 AM.png > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1583) Clang tool build improvement "include what you use"
[ https://issues.apache.org/jira/browse/MESOS-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-1583: -- Attachment: Screen Shot 2014-07-16 at 11.56.01 AM.png IWYU screenshot > Clang tool build improvement "include what you use" > --- > > Key: MESOS-1583 > URL: https://issues.apache.org/jira/browse/MESOS-1583 > Project: Mesos > Issue Type: Improvement > Components: technical debt >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > Attachments: Screen Shot 2014-07-16 at 11.56.01 AM.png > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1583) Clang tool build improvement "include what you use"
[ https://issues.apache.org/jira/browse/MESOS-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069164#comment-14069164 ] Isabel Jimenez commented on MESOS-1583: --- After tests on small sections I note the controversy was founded. Since it's not obvious to make IWYU launch with Mesos I pushed Docker [images|https://hub.docker.com/u/jimenez/] to their registry and the Dockerfiles can also be found [here|https://github.com/jimenez/Dockerfiles]. I am also attaching a screenshot of an example that make me conclude on not using IWYU to remove unnecessary header inclusions. > Clang tool build improvement "include what you use" > --- > > Key: MESOS-1583 > URL: https://issues.apache.org/jira/browse/MESOS-1583 > Project: Mesos > Issue Type: Improvement > Components: technical debt >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-1604) LowLevelSchedulerLibprocess did not receive offers from Master
[
https://issues.apache.org/jira/browse/MESOS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone resolved MESOS-1604.
---
Resolution: Fixed
Fix Version/s: 0.20.0
Assignee: Zuyu Zhang
commit 8327209a47210ccfd18d65b39355256bb3065b84
Author: Zuyu Zhang
Date: Mon Jul 21 12:40:58 2014 -0700
Fixed the checkpoint configuration bug in example frameworks.
Review: https://reviews.apache.org/r/23561
> LowLevelSchedulerLibprocess did not receive offers from Master
> --
>
> Key: MESOS-1604
> URL: https://issues.apache.org/jira/browse/MESOS-1604
> Project: Mesos
> Issue Type: Bug
> Environment: cent os
>Reporter: Zuyu Zhang
>Assignee: Zuyu Zhang
> Fix For: 0.20.0
>
>
> {noformat}
> [ RUN ] ExamplesTest.LowLevelSchedulerLibprocess
> Using temporary directory
> '/tmp/ExamplesTest_LowLevelSchedulerLibprocess_MT54ja'
> Enabling checkpoint for the framework
> Enabling authentication for the scheduler
> I0715 18:51:48.456028 2019271440 scheduler.cpp:132] Version: 0.20.0
> I0715 18:51:48.459760 2019271440 leveldb.cpp:176] Opened db in 1764us
> I0715 18:51:48.460237 2019271440 leveldb.cpp:183] Compacted db in 463us
> I0715 18:51:48.460283 2019271440 leveldb.cpp:198] Created db iterator in 24us
> I0715 18:51:48.460311 2019271440 leveldb.cpp:204] Seeked to beginning of db
> in 15us
> I0715 18:51:48.460337 2019271440 leveldb.cpp:273] Iterated through 0 keys in
> the db in 18us
> I0715 18:51:48.460381 2019271440 replica.cpp:741] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0715 18:51:48.461017 222433280 recover.cpp:425] Starting replica recovery
> I0715 18:51:48.461197 222433280 recover.cpp:451] Replica is in EMPTY status
> I0715 18:51:48.461845 222433280 replica.cpp:638] Replica in EMPTY status
> received a broadcasted recover request
> I0715 18:51:48.462077 220823552 recover.cpp:188] Received a recover response
> from a replica in EMPTY status
> I0715 18:51:48.462210 220823552 recover.cpp:542] Updating replica status to
> STARTING
> I0715 18:51:48.462533 222433280 leveldb.cpp:306] Persisting metadata (8
> bytes) to leveldb took 288us
> I0715 18:51:48.462589 222433280 replica.cpp:320] Persisted replica status to
> STARTING
> I0715 18:51:48.462645 220823552 master.cpp:288] Master
> 20140715-185148-16777343-58730-32992 (localhost) started on 127.0.0.1:58730
> I0715 18:51:48.462714 220823552 master.cpp:325] Master only allowing
> authenticated frameworks to register
> I0715 18:51:48.462739 220823552 master.cpp:332] Master allowing
> unauthenticated slaves to register
> I0715 18:51:48.462757 220823552 credentials.hpp:36] Loading credentials for
> authentication from
> '/tmp/ExamplesTest_LowLevelSchedulerLibprocess_MT54ja/credentials'
> W0715 18:51:48.462885 220823552 credentials.hpp:51] Permissions on
> credentials file
> '/tmp/ExamplesTest_LowLevelSchedulerLibprocess_MT54ja/credentials' are too
> open. It is recommended that your credentials file is NOT accessible by
> others.
> I0715 18:51:48.462924 2019271440 containerizer.cpp:124] Using isolation:
> posix/cpu,posix/mem
> I0715 18:51:48.462988 220823552 master.cpp:359] Authorization enabled
> I0715 18:51:48.463070 220286976 recover.cpp:451] Replica is in STARTING status
> I0715 18:51:48.463729 219750400 replica.cpp:638] Replica in STARTING status
> received a broadcasted recover request
> I0715 18:51:48.463878 222433280 slave.cpp:168] Slave started on
> 1)@127.0.0.1:58730
> I0715 18:51:48.464135 221896704 recover.cpp:188] Received a recover response
> from a replica in STARTING status
> I0715 18:51:48.464149 222433280 slave.cpp:279] Slave resources: cpus(*):4;
> mem(*):7168; disk(*):470714; ports(*):[31000-32000]
> I0715 18:51:48.464359 2019271440 containerizer.cpp:124] Using isolation:
> posix/cpu,posix/mem
> I0715 18:51:48.464381 222433280 slave.cpp:324] Slave hostname: localhost
> I0715 18:51:48.464397 222433280 slave.cpp:325] Slave checkpoint: false
> I0715 18:51:48.464488 219213824 recover.cpp:542] Updating replica status to
> VOTING
> I0715 18:51:48.464767 222969856 leveldb.cpp:306] Persisting metadata (8
> bytes) to leveldb took 191us
> I0715 18:51:48.464807 222969856 replica.cpp:320] Persisted replica status to
> VOTING
> I0715 18:51:48.464859 222969856 recover.cpp:556] Successfully joined the
> Paxos group
> I0715 18:51:48.465044 219750400 state.cpp:33] Recovering state from
> '/Users/zuyuzhang/workspace/mesos/build-clang/mesos-FxDHkE/0/meta'
> I0715 18:51:48.465116 222969856 recover.cpp:440] Recover process terminated
> I0715 18:51:48.465334 220823552 status_update_manager.cpp:193] Recovering
> status update manager
> I0715 18:51:48.465350 221896704 master.cpp:1128] The newly elected leader is
> master@127.0.0.1:58730 with id 20140715-185148
[jira] [Created] (MESOS-1620) Reconciliation does not send back tasks pending validation / authorization.
Benjamin Mahler created MESOS-1620: -- Summary: Reconciliation does not send back tasks pending validation / authorization. Key: MESOS-1620 URL: https://issues.apache.org/jira/browse/MESOS-1620 Project: Mesos Issue Type: Bug Reporter: Benjamin Mahler Assignee: Benjamin Mahler Per Vinod's feedback on https://reviews.apache.org/r/23542/, we do not send back TASK_STAGING for those tasks that are pending in the Master (validation / authorization still in progress). For both implicit and explicit task reconciliation, the master could reply with TASK_STAGING for these tasks, as this provides additional information to the framework. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-757) The post-reviews.py script hangs if HTTP authentication has expired
[ https://issues.apache.org/jira/browse/MESOS-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-757: -- Labels: newbie (was: ) > The post-reviews.py script hangs if HTTP authentication has expired > --- > > Key: MESOS-757 > URL: https://issues.apache.org/jira/browse/MESOS-757 > Project: Mesos > Issue Type: Bug >Reporter: Benjamin Hindman > Labels: newbie > > If you run post-reviews.py and your HTTP authentication information has > expired then the script will just hang. Short term fix is to run post-review > by itself so you can re-authenticate. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1316) Implement decent unit test coverage for the mesos-fetcher tool
[
https://issues.apache.org/jira/browse/MESOS-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068855#comment-14068855
]
Bernd Mathiske commented on MESOS-1316:
---
"Ben has offered to reinstate the tests."
What does this mean?
> Implement decent unit test coverage for the mesos-fetcher tool
> --
>
> Key: MESOS-1316
> URL: https://issues.apache.org/jira/browse/MESOS-1316
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Tom Arnfeld
>Assignee: Benjamin Hindman
>
> There are current no tests that cover the {{mesos-fetcher}} tool itself, and
> hence bugs like MESOS-1313 have accidentally slipped though.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (MESOS-1619) OsTest.User test is flaky
[ https://issues.apache.org/jira/browse/MESOS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068844#comment-14068844 ] Ian Downes commented on MESOS-1619: --- This looks to be a configuration issue on the host. Is there a valid /etc/master.passwd on the host? Do other cli operations like `id` function? > OsTest.User test is flaky > - > > Key: MESOS-1619 > URL: https://issues.apache.org/jira/browse/MESOS-1619 > Project: Mesos > Issue Type: Bug > Components: test > Environment: centos7 w/ gcc >Reporter: Vinod Kone > > [ RUN ] OsTest.user > stout/tests/os_tests.cpp:720: Failure > Value of: os::getuid(UUID::random().toString()).isNone() > Actual: false > Expected: true > stout/tests/os_tests.cpp:721: Failure > Value of: os::getgid(UUID::random().toString()).isNone() > Actual: false > Expected: true > WARNING: Logging before InitGoogleLogging() is written to STDERR > E0721 06:15:58.656255 13440 os.hpp:731] Failed to set gid: Failed to get > username information: No such file or directory > [ FAILED ] OsTest.user (20 ms) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1619) OsTest.User test is flaky
Vinod Kone created MESOS-1619: - Summary: OsTest.User test is flaky Key: MESOS-1619 URL: https://issues.apache.org/jira/browse/MESOS-1619 Project: Mesos Issue Type: Bug Components: test Environment: centos7 w/ gcc Reporter: Vinod Kone [ RUN ] OsTest.user stout/tests/os_tests.cpp:720: Failure Value of: os::getuid(UUID::random().toString()).isNone() Actual: false Expected: true stout/tests/os_tests.cpp:721: Failure Value of: os::getgid(UUID::random().toString()).isNone() Actual: false Expected: true WARNING: Logging before InitGoogleLogging() is written to STDERR E0721 06:15:58.656255 13440 os.hpp:731] Failed to set gid: Failed to get username information: No such file or directory [ FAILED ] OsTest.user (20 ms) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1593) Add DockerInfo Configuration
[ https://issues.apache.org/jira/browse/MESOS-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068631#comment-14068631 ] Timothy St. Clair commented on MESOS-1593: -- +1 [~gabrtv] imho the following are critical: - Pod approach from the inception. You may want to take a page from the google's manifest. https://developers.google.com/compute/docs/containers/container_vms#container_manifest - Enabling args to override * mesos defaults, I saw in some of the reviews defaults provided. Args should trump. > Add DockerInfo Configuration > > > Key: MESOS-1593 > URL: https://issues.apache.org/jira/browse/MESOS-1593 > Project: Mesos > Issue Type: Task >Reporter: Timothy Chen >Assignee: Timothy Chen > > We want to add a new proto message to encapsulate all Docker related > configurations into DockerInfo. > Here is the document that describes the design for DockerInfo: > https://github.com/tnachen/mesos/wiki/DockerInfo-design -- This message was sent by Atlassian JIRA (v6.2#6252)
