You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jan Schlicht (JIRA)" <ji...@apache.org> on 2015/12/03 11:04:10 UTC

[jira] [Commented] (MESOS-4055) SSL-related test fail reliably in optimized build

    [ https://issues.apache.org/jira/browse/MESOS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037596#comment-15037596 ] 

Jan Schlicht commented on MESOS-4055:
-------------------------------------

This may be an OpenSSL or Ubuntu issue? With Fedora 23, gcc 5.1.1 and a {{../configure --enable-ssl --enable-libevent --enable-optimized}} build, there are no errors in {{SSLTest}} for me.

> SSL-related test fail reliably in optimized build
> -------------------------------------------------
>
>                 Key: MESOS-4055
>                 URL: https://issues.apache.org/jira/browse/MESOS-4055
>             Project: Mesos
>          Issue Type: Task
>          Components: libprocess, 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}
> most SSL-related tests fail reliably with SIGSEV. The full list of failing tests is
> {code}
> SSL.Disabled
> SSLTest.BasicSameProcess
> SSLTest.SSLSocket
> SSLTest.NonSSLSocket
> SSLTest.NoVerifyBadCA
> SSLTest.RequireBadCA
> SSLTest.VerifyBadCA
> SSLTest.VerifyCertificate
> SSLTest.RequireCertificate
> SSLTest.ProtocolMismatch
> SSLTest.ValidDowngrade
> SSLtest.NoValidDowngrade
> SSLTest.NoValidDowngrade
> SSLTest.ValidDowngradeEachProtocol
> SSLTest.NoValidDowngradeEachProtocol
> SSLTest.PeerAddress
> SSLTest.HTTPSGet
> SSLTest.HTTPSPost
> {code}
> The test fail with {{SIGSEV}} or similarly worrisome reasons, e.g.,
> {code}
> [ RUN      ] SSLTest.SSLSocket
> *** Aborted at 1449135851 (unix time) try "date -d @1449135851" if you are using GNU date ***
> PC: @           0x4418f4 Try<>::~Try()
> *** SIGSEGV (@0x5acce6) received by PID 29976 (TID 0x7fe601eb5780) from PID 5950694; stack trace: ***
>     @     0x7fe601a9a340 (unknown)
>     @           0x4418f4 Try<>::~Try()
>     @           0x5a843c SSLTest::setup_server()
>     @           0x595162 SSLTest_SSLSocket_Test::TestBody()
>     @           0x5f2428 testing::internal::HandleSehExceptionsInMethodIfSupported<>()
>     @           0x5ec880 testing::internal::HandleExceptionsInMethodIfSupported<>()
>     @           0x5cd0ff testing::Test::Run()
>     @           0x5cd882 testing::TestInfo::Run()
>     @           0x5cdec8 testing::TestCase::Run()
>     @           0x5d4610 testing::internal::UnitTestImpl::RunAllTests()
>     @           0x5f3203 testing::internal::HandleSehExceptionsInMethodIfSupported<>()
>     @           0x5ed5f4 testing::internal::HandleExceptionsInMethodIfSupported<>()
>     @           0x5d33ac testing::UnitTest::Run()
>     @           0x40fd70 main
>     @     0x7fe600024ec5 (unknown)
>     @           0x413eb1 (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)