Benjamin Bannier created MESOS-4057:
---------------------------------------
Summary: RegistryClientTest suite fails reliably in optimized build
Key: MESOS-4057
URL: https://issues.apache.org/jira/browse/MESOS-4057
Project: Mesos
Issue Type: Bug
Components: test
Affects Versions: 0.26.0
Reporter: Benjamin Bannier
Under ubuntu14.04 building 5c0e4dc using gcc-4.8.4-2ubuntu1~14.04 with
{code}
% ../configure --enable-ssl --enable-libevent --enable-optimized
{code}
all six tests from the {{RegistryClientTest}} suite fail with SIGSEV. The full
list of failing tests is
{code}
RegistryClientTest.SimpleGetToken
RegistryClientTest.BadTokenResponse
RegistryClientTest.SimpleGetManifest
RegistryClientTest.SimpleGetBlob
RegistryClientTest.BadRequest
RegistryClientTest.SimpleRegistryPuller
{code}
The failure messages are similar, e.g..
{code}
[ RUN ] RegistryClientTest.BadTokenResponse
*** Aborted at 1449146245 (unix time) try "date -d @1449146245" if you are
using GNU date ***
PC: @ 0x7f1c5c5ba6ad (unknown)
*** SIGSEGV (@0xa24888) received by PID 21542 (TID 0x7f1c61f24800) from PID
10635400; stack trace: ***
@ 0x7f1c5be35340 (unknown)
@ 0x7f1c5c5ba6ad (unknown)
@ 0x7f1c5c61932f (unknown)
@ 0x14067aa Try<>::~Try()
@ 0x1406ab0 SSLTest::setup_server()
@ 0x140869b mesos::internal::tests::RegistryClientTest::getServer()
@ 0x13f315a
mesos::internal::tests::RegistryClientTest_BadTokenResponse_Test::TestBody()
@ 0x14ec3b0
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x14e728a
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x14c8993 testing::Test::Run()
@ 0x14c9116 testing::TestInfo::Run()
@ 0x14c975c testing::TestCase::Run()
@ 0x14cfea4 testing::internal::UnitTestImpl::RunAllTests()
@ 0x14ecfd5
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x14e7e00
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x14cec40 testing::UnitTest::Run()
@ 0xd045c4 RUN_ALL_TESTS()
@ 0xd041b1 main
@ 0x7f1c5ba81ec5 (unknown)
@ 0x930bb9 (unknown)
Segmentation fault
{code}
Even though we do not typically release optimized builds we should still look
into these as optimizations tend to expose fragile constructs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
