You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Greg Mann (JIRA)" <ji...@apache.org> on 2015/08/28 19:13:45 UTC
[jira] [Commented] (MESOS-2879) Random recursive_mutex errors in
when running make check
[ https://issues.apache.org/jira/browse/MESOS-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720252#comment-14720252 ]
Greg Mann commented on MESOS-2879:
----------------------------------
Currently, running {{build/3rdparty/libprocess/tests}} on OSX 10.10.4 will produce this error reliably after successful completion of the libprocess tests:
{code}
libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentlibc++abi.dylib: libc++abi.dylib:
*** Aborted at 1440781017 (unix time) try "date -d @1440781017" if you are using GNU date ***
PC: @ 0x7fff8e34e286 __pthread_kill
terminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argument*** SIGABRT (@0x7fff8e34e286) received by PID 41187 (TID 0x101ea6000) stack trace: ***
@ 0x7fff91651f1a _sigtramp
@ 0x101ea4fa8 (unknown)
terminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argument @ 0x7fff8da689b3 abort
@ 0x7fff8ff31a21 abort_message
@ 0x7fff8ff599b9 default_terminate_handler()
@ 0x7fff8a00f7eb _objc_terminate()
@ 0x7fff8ff570a1 std::__terminate()
@ 0x7fff8ff56b30 __cxa_throw
@ 0x7fff97146b25 std::__1::__throw_system_error()
{code}
However, after applying the patch for MESOS-3158 (found at https://reviews.apache.org/r/37821/), these errors go away. Not sure what you have in the works for this ticket [~jvanremoortere], but perhaps that patch is a satisfactory solution?
> Random recursive_mutex errors in when running make check
> --------------------------------------------------------
>
> Key: MESOS-2879
> URL: https://issues.apache.org/jira/browse/MESOS-2879
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Reporter: Alexander Rojas
> Assignee: Joris Van Remoortere
> Labels: mesosphere, tech-debt
>
> While running make check on OS X, from time to time {{recursive_mutex}} errors appear after running all the test successfully. Just one of the experience messages actually stops {{make check}} reporting an error.
> The following error messages have been experienced:
> {code}
> libc++abi.dylib: libc++abi.dylib: libc++abi.dylib: libc++abi.dylib: libc++abi.dylib: libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argument
> *** Aborted at 1434553937 (unix time) try "date -d @1434553937" if you are using GNU date ***
> {code}
> {code}
> libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argument
> *** Aborted at 1434557001 (unix time) try "date -d @1434557001" if you are using GNU date ***
> libc++abi.dylib: PC: @ 0x7fff93855286 __pthread_kill
> libc++abi.dylib: *** SIGABRT (@0x7fff93855286) received by PID 88060 (TID 0x10fc40000) stack trace: ***
> @ 0x7fff8e1d6f1a _sigtramp
> libc++abi.dylib: @ 0x10fc3f1a8 (unknown)
> libc++abi.dylib: @ 0x7fff979deb53 abort
> libc++abi.dylib: libc++abi.dylib: libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentterminating with uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argumentMaking check in include
> {code}
> {code}
> Assertion failed: (e == 0), function ~recursive_mutex, file /SourceCache/libcxx/libcxx-120/src/mutex.cpp, line 82.
> *** Aborted at 1434555685 (unix time) try "date -d @1434555685" if you are using GNU date ***
> PC: @ 0x7fff93855286 __pthread_kill
> *** SIGABRT (@0x7fff93855286) received by PID 60235 (TID 0x7fff7ebdc300) stack trace: ***
> @ 0x7fff8e1d6f1a _sigtramp
> @ 0x10b512350 google::CheckNotNull<>()
> @ 0x7fff979deb53 abort
> @ 0x7fff979a6c39 __assert_rtn
> @ 0x7fff9bffdcc9 std::__1::recursive_mutex::~recursive_mutex()
> @ 0x10b881928 process::ProcessManager::~ProcessManager()
> @ 0x10b874445 process::ProcessManager::~ProcessManager()
> @ 0x10b874418 process::finalize()
> @ 0x10b2f7aec main
> @ 0x7fff98edc5c9 start
> make[5]: *** [check-local] Abort trap: 6
> make[4]: *** [check-am] Error 2
> make[3]: *** [check-recursive] Error 1
> make[2]: *** [check-recursive] Error 1
> make[1]: *** [check] Error 2
> make: *** [check-recursive] Error 1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)