Description
I saw the following in an rpc_server-test unit test failure:
F0519 15:03:51.615512 16049 mutex.cc:77] Check failed: 0 == rv (0 vs. 16) . Device or resource busy *** Check failure stack trace: *** *** Aborted at 1526767431 (unix time) try "date -d @1526767431" if you are using GNU date *** PC: @ 0x373b032625 __GI_raise *** SIGABRT (@0x45200003eb1) received by PID 16049 (TID 0x7f6bf0f84980) from PID 16049; stack trace: *** @ 0x373b40f710 (unknown) at ??:0 @ 0x373b032625 __GI_raise at ??:0 @ 0x373b033e05 __GI_abort at ??:0 @ 0x7f6bf1458a29 google::logging_fail() at ??:0 @ 0x7f6bf145a31d google::LogMessage::Fail() at ??:0 @ 0x7f6bf145c1dd google::LogMessage::SendToLog() at ??:0 @ 0x7f6bf1459e59 google::LogMessage::Flush() at ??:0 @ 0x7f6bf145cc7f google::LogMessageFatal::~LogMessageFatal() at ??:0 @ 0x7f6bf397773a kudu::Mutex::~Mutex() at ??:0 @ 0x7f6bf39b87bb kudu::ThreadMgr::~ThreadMgr() at ??:0 @ 0x7f6bf39be504 std::_Sp_counted_ptr<>::_M_dispose() at ??:0 @ 0x412a14 std::_Sp_counted_base<>::_M_release() at /opt/rh/devtoolset-3/root/usr/include/c++/4.9.2/bits/shared_ptr_base.h:163 @ 0x4121f3 std::__shared_count<>::~__shared_count() at /opt/rh/devtoolset-3/root/usr/include/c++/4.9.2/bits/shared_ptr_base.h:667 @ 0x7f6bf39b86ca std::__shared_ptr<>::~__shared_ptr() at ??:0 @ 0x7f6bf39b86e4 std::shared_ptr<>::~shared_ptr() at ??:0 @ 0x373b035ebd __cxa_finalize at ??:0 @ 0x7f6bf38b60a3 (unknown) at ??:0 @ 0x373ac0ec3c _dl_fini at ??:0 @ 0x373b035b22 __GI_exit at ??:0 @ 0x373b01ed64 __libc_start_main at ??:0 @ 0x40e739 (unknown) at ??:0