[jira] [Created] (MESOS-1698) make check segfaults
Vinod Kone created MESOS-1698:
-
Summary: make check segfaults
Key: MESOS-1698
URL: https://issues.apache.org/jira/browse/MESOS-1698
Project: Mesos
Issue Type: Bug
Components: test
Environment: Ubuntu
Reporter: Vinod Kone
Observed this on Apache CI:
https://builds.apache.org/job/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/2331/consoleFull
It looks like the segfault happens before any tests are run. So I suspect
somewhere in the setup phase of the tests.
{code}
mv -f .deps/tests-time_tests.Tpo .deps/tests-time_tests.Po
/bin/bash ./libtool --tag=CXX --mode=link g++ -g -g2 -O2
-Wno-unused-local-typedefs -std=c++11 -o tests tests-decoder_tests.o
tests-encoder_tests.o tests-http_tests.o tests-io_tests.o tests-main.o
tests-mutex_tests.o tests-metrics_tests.o tests-owned_tests.o
tests-process_tests.o tests-queue_tests.o tests-reap_tests.o
tests-sequence_tests.o tests-shared_tests.o tests-statistics_tests.o
tests-subprocess_tests.o tests-system_tests.o tests-timeseries_tests.o
tests-time_tests.o 3rdparty/libgmock.la libprocess.la
3rdparty/glog-0.3.3/libglog.la 3rdparty/libry_http_parser.la
3rdparty/libev-4.15/libev.la -lz -lrt
libtool: link: g++ -g -g2 -O2 -Wno-unused-local-typedefs -std=c++11 -o tests
tests-decoder_tests.o tests-encoder_tests.o tests-http_tests.o tests-io_tests.o
tests-main.o tests-mutex_tests.o tests-metrics_tests.o tests-owned_tests.o
tests-process_tests.o tests-queue_tests.o tests-reap_tests.o
tests-sequence_tests.o tests-shared_tests.o tests-statistics_tests.o
tests-subprocess_tests.o tests-system_tests.o tests-timeseries_tests.o
tests-time_tests.o 3rdparty/.libs/libgmock.a ./.libs/libprocess.a
/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess/3rdparty/glog-0.3.3/.libs/libglog.a
/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess/3rdparty/libev-4.15/.libs/libev.a
3rdparty/glog-0.3.3/.libs/libglog.a -lpthread
3rdparty/.libs/libry_http_parser.a 3rdparty/libev-4.15/.libs/libev.a -lm -lz
-lrt
make[5]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
make check-local
make[5]: Entering directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
./tests
Note: Google Test filter =
[==] Running 0 tests from 0 test cases.
[==] 0 tests from 0 test cases ran. (0 ms total)
[ PASSED ] 0 tests.
YOU HAVE 3 DISABLED TESTS
make[5]: *** [check-local] Segmentation fault
make[5]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
make[4]: *** [check-am] Error 2
make[4]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty'
make[1]: *** [check] Error 2
make[1]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty'
make: *** [check-recursive] Error 1
Build step 'Execute shell' marked build as failure
Sending e-mails to: d...@mesos.apache.org benjamin.hind...@gmail.com
dha...@twitter.com yujie@gmail.com
Finished: FAILURE
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (MESOS-1699) OsTest(s) sometimes are stuck forever
Vinod Kone created MESOS-1699:
-
Summary: OsTest(s) sometimes are stuck forever
Key: MESOS-1699
URL: https://issues.apache.org/jira/browse/MESOS-1699
Project: Mesos
Issue Type: Bug
Components: test
Affects Versions: 0.20.0
Reporter: Vinod Kone
Observed this quite a few times on the Apache CI. The tests timeout somewhere
in the OsTests.
E.g:
https://builds.apache.org/job/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Disable-Java-Disable-Python-Disable-Webui/2310/consoleText
{code}
[--] 20 tests from OsTest
[ RUN ] OsTest.find
[ OK ] OsTest.find (1 ms)
[ RUN ] OsTest.system
sh: 1: invalid.command: not found
[ OK ] OsTest.system (43 ms)
[ RUN ] OsTest.release
[ OK ] OsTest.release (1 ms)
[ RUN ] OsTest.sysname
[ OK ] OsTest.sysname (0 ms)
[ RUN ] OsTest.uname
[ OK ] OsTest.uname (0 ms)
[ RUN ] OsTest.process
[ OK ] OsTest.process (0 ms)
[ RUN ] OsTest.touch
[ OK ] OsTest.touch (1 ms)
[ RUN ] OsTest.pstree
Build timed out (after 180 minutes). Marking the build as failed.
Build was aborted
Sending e-mails to: d...@mesos.apache.org benjamin.hind...@gmail.com
make[5]: *** wait: No child processes. Stop.
make[5]: *** Waiting for unfinished jobs
make[5]: *** wait: No child processes. Stop.
make[3]: make[2]: *** [check-recursive] Terminated
*** [check-recursive] Terminated
make[4]: *** [check] Error 2
make: *** [check-recursive] Terminated
make[1]: *** [check] Terminated
Finished: FAILURE
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (MESOS-1700) ThreadLocal does not release pthread keys or log properly.
[ https://issues.apache.org/jira/browse/MESOS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-1700: --- Sprint: Q3 Sprint 3 ThreadLocal does not release pthread keys or log properly. -- Key: MESOS-1700 URL: https://issues.apache.org/jira/browse/MESOS-1700 Project: Mesos Issue Type: Bug Components: stout Reporter: Benjamin Mahler Assignee: Benjamin Mahler The ThreadLocalT abstraction in stout does not release the allocated pthread keys upon destruction: https://github.com/apache/mesos/blob/0.19.1/3rdparty/libprocess/3rdparty/stout/include/stout/thread.hpp#L22 It also does not log the errors correctly. Fortunately this does not impact mesos at the current time. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1700) ThreadLocal does not release pthread keys or log properly.
[ https://issues.apache.org/jira/browse/MESOS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096175#comment-14096175 ] Benjamin Mahler commented on MESOS-1700: https://reviews.apache.org/r/24669/ ThreadLocal does not release pthread keys or log properly. -- Key: MESOS-1700 URL: https://issues.apache.org/jira/browse/MESOS-1700 Project: Mesos Issue Type: Bug Components: stout Reporter: Benjamin Mahler Assignee: Benjamin Mahler The ThreadLocalT abstraction in stout does not release the allocated pthread keys upon destruction: https://github.com/apache/mesos/blob/0.19.1/3rdparty/libprocess/3rdparty/stout/include/stout/thread.hpp#L22 It also does not log the errors correctly. Fortunately this does not impact mesos at the current time. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1698) make check segfaults
[
https://issues.apache.org/jira/browse/MESOS-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-1698:
--
Sprint: Q3 Sprint 3
Story Points: 2
make check segfaults
Key: MESOS-1698
URL: https://issues.apache.org/jira/browse/MESOS-1698
Project: Mesos
Issue Type: Bug
Components: test
Environment: Ubuntu
Reporter: Vinod Kone
Assignee: Vinod Kone
Observed this on Apache CI:
https://builds.apache.org/job/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/2331/consoleFull
It looks like the segfault happens before any tests are run. So I suspect
somewhere in the setup phase of the tests.
{code}
mv -f .deps/tests-time_tests.Tpo .deps/tests-time_tests.Po
/bin/bash ./libtool --tag=CXX --mode=link g++ -g -g2 -O2
-Wno-unused-local-typedefs -std=c++11 -o tests tests-decoder_tests.o
tests-encoder_tests.o tests-http_tests.o tests-io_tests.o tests-main.o
tests-mutex_tests.o tests-metrics_tests.o tests-owned_tests.o
tests-process_tests.o tests-queue_tests.o tests-reap_tests.o
tests-sequence_tests.o tests-shared_tests.o tests-statistics_tests.o
tests-subprocess_tests.o tests-system_tests.o tests-timeseries_tests.o
tests-time_tests.o 3rdparty/libgmock.la libprocess.la
3rdparty/glog-0.3.3/libglog.la 3rdparty/libry_http_parser.la
3rdparty/libev-4.15/libev.la -lz -lrt
libtool: link: g++ -g -g2 -O2 -Wno-unused-local-typedefs -std=c++11 -o tests
tests-decoder_tests.o tests-encoder_tests.o tests-http_tests.o
tests-io_tests.o tests-main.o tests-mutex_tests.o tests-metrics_tests.o
tests-owned_tests.o tests-process_tests.o tests-queue_tests.o
tests-reap_tests.o tests-sequence_tests.o tests-shared_tests.o
tests-statistics_tests.o tests-subprocess_tests.o tests-system_tests.o
tests-timeseries_tests.o tests-time_tests.o 3rdparty/.libs/libgmock.a
./.libs/libprocess.a
/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess/3rdparty/glog-0.3.3/.libs/libglog.a
/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess/3rdparty/libev-4.15/.libs/libev.a
3rdparty/glog-0.3.3/.libs/libglog.a -lpthread
3rdparty/.libs/libry_http_parser.a 3rdparty/libev-4.15/.libs/libev.a -lm -lz
-lrt
make[5]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
make check-local
make[5]: Entering directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
./tests
Note: Google Test filter =
[==] Running 0 tests from 0 test cases.
[==] 0 tests from 0 test cases ran. (0 ms total)
[ PASSED ] 0 tests.
YOU HAVE 3 DISABLED TESTS
make[5]: *** [check-local] Segmentation fault
make[5]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
make[4]: *** [check-am] Error 2
make[4]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty/libprocess'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty'
make[1]: *** [check] Error 2
make[1]: Leaving directory
`/home/jenkins/jenkins-slave/workspace/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Set-JAVA_HOME/build/3rdparty'
make: *** [check-recursive] Error 1
Build step 'Execute shell' marked build as failure
Sending e-mails to: d...@mesos.apache.org benjamin.hind...@gmail.com
dha...@twitter.com yujie@gmail.com
Finished: FAILURE
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (MESOS-1629) GLOG Initialized twice if the Framework Scheduler also uses GLOG
[
https://issues.apache.org/jira/browse/MESOS-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096387#comment-14096387
]
Vinod Kone commented on MESOS-1629:
---
https://reviews.apache.org/r/24687/
GLOG Initialized twice if the Framework Scheduler also uses GLOG
Key: MESOS-1629
URL: https://issues.apache.org/jira/browse/MESOS-1629
Project: Mesos
Issue Type: Bug
Reporter: Zuyu Zhang
Assignee: Vinod Kone
{noformat}
Could not create logging file: No such file or directory
COULD NOT CREATE A LOGGINGFILE 20140722-205220.31450!F0722 20:52:20.494424
31450 utilities.cc:317] Check failed: !IsGoogleLoggingInitialized() You
called InitGoogleLogging() twice!
*** Check failure stack trace: ***
@ 0x4399ce google::LogMessage::Fail()
@ 0x43991d google::LogMessage::SendToLog()
@ 0x43932e google::LogMessage::Flush()
@ 0x43c0e5 google::LogMessageFatal::~LogMessageFatal()
@ 0x44089f
google::glog_internal_namespace_::InitGoogleLoggingUtilities()
@ 0x43c409 google::InitGoogleLogging()
@ 0x7f0bdd43b55c mesos::internal::logging::initialize()
@ 0x7f0bdcf9564d mesos::scheduler::MesosProcess::MesosProcess()
@ 0x7f0bdcf92de0 mesos::scheduler::Mesos::Mesos()
@ 0x421483 heron::mesos::Scheduler::Scheduler()
@ 0x4305dc main
@ 0x7f0bd97159c4 __libc_start_main
@ 0x420869 (unknown)
Aborted
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
