You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Meng Zhu (JIRA)" <ji...@apache.org> on 2019/01/09 01:46:00 UTC

[jira] [Created] (MESOS-9515) `DefaultExecutorTest.KillMultipleTasks` is flaky.

Meng Zhu created MESOS-9515:
-------------------------------

             Summary: `DefaultExecutorTest.KillMultipleTasks` is flaky.
                 Key: MESOS-9515
                 URL: https://issues.apache.org/jira/browse/MESOS-9515
             Project: Mesos
          Issue Type: Bug
            Reporter: Meng Zhu
         Attachments: DefaultExecutorTest_KillMultipleTasks_badrun.txt

Failure observed on our CI:
debian-8-SSL

Attached log: DefaultExecutorTest_KillMultipleTasks_badrun.txt

Error:
Segfault at `mesos::v1::scheduler::Mesos::send()`

{noformat}
I0109 01:32:00.147313 28457 hierarchical.cpp:348] Removed framework 0dbceb47-8557-446b-9d11-f0c05bf40682-0000
*** Aborted at 1546997520 (unix time) try "date -d @1546997520" if you are using GNU date ***
PC: @     0x7ffafc715523 mesos::v1::scheduler::Mesos::send()
*** SIGSEGV (@0x0) received by PID 4008 (TID 0x7ffaee038700) from PID 0; stack trace: ***
    @     0x7ffade0feabc (unknown)
    @     0x7ffade103751 (unknown)
    @     0x7ffade0f6f58 (unknown)
    @     0x7ffaf98da890 (unknown)
    @     0x7ffafc715523 mesos::v1::scheduler::Mesos::send()
    @     0x55cfa3b8ce18 _ZNK5mesos8internal5tests2v19scheduler23SendAcknowledgeActionP2INS_2v111FrameworkIDENS5_7AgentIDEE10gmock_ImplIFvPNS5_9scheduler5MesosERKNSA_12Event_UpdateEEE17gmock_PerformImplISC_SF_N7testing8internal12ExcessiveArgESL_SL_SL_SL_SL_SL_SL_EEvRKSt5tupleIJSC_SF_EET_T0_T1_T2_T3_T4_T5_T6_T7_T8_
    @     0x55cfa3b8cfa0 _ZN5mesos8internal5tests2v19scheduler23SendAcknowledgeActionP2INS_2
{noformat}

Looks like the classic race between test shutdown and scheduler sending task status acknowledgement here: https://github.com/apache/mesos/blob/3478e344fb77d931f6122980c6e94cd3913c441d/src/tests/default_executor_tests.cpp#L724



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)