Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-8797

Check failed in the default executor while running `MesosContainerizer/DefaultExecutorTest.TaskUsesExecutor/0` test.

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.8.0
    • executor
    • Centos 7 SSL (internal CI)
      master-a95d9b8 (17-Apr-2018 14:03:14)

    Description

      lt-mesos-default-executor: ../../3rdparty/stout/include/stout/option.hpp:119: T& Option<T>::get() & [with T = std::basic_string<char>]: Assertion `isSome()' failed.
      *** Aborted at 1523976443 (unix time) try "date -d @1523976443" if you are using GNU date ***
      PC: @ 0x7efcfd11f1f7 __GI_raise
      *** SIGABRT (@0x4d44) received by PID 19780 (TID 0x7efcf5adb700) from PID 19780; stack trace: ***
      @ 0x7efcfd9da5e0 (unknown)
      @ 0x7efcfd11f1f7 __GI_raise
      @ 0x7efcfd1208e8 __GI_abort
      @ 0x7efcfd118266 __assert_fail_base
      @ 0x7efcfd118312 __GI___assert_fail
      @ 0x55a05fa269f7 mesos::internal::DefaultExecutor::waited()
      @ 0x7efd002212d1 process::ProcessBase::consume()
      @ 0x7efd0023a52a process::ProcessManager::resume()
      @ 0x7efd0023dfa6 _ZNSt6thread5_ImplISt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvEUlvE_vEEE6_M_runEv
      @ 0x7efd003f9470 execute_native_thread_routine
      @ 0x7efcfd9d2e25 start_thread
      @ 0x7efcfd1e234d __clone
      

      Observed this failure in internal CI for test

       MesosContainerizer/DefaultExecutorTest.TaskUsesExecutor/0

      Attachments

        Activity

          gilbert Gilbert Song added a comment -

          Took a quick look, this may be caused by https://github.com/apache/mesos/blob/master/src/launcher/default_executor.cpp#L938

          for some cases, e.g., container is in killing state, the optional `message` is none.

          gilbert Gilbert Song added a comment - Took a quick look, this may be caused by https://github.com/apache/mesos/blob/master/src/launcher/default_executor.cpp#L938 for some cases, e.g., container is in killing state, the optional `message` is none.
          bennoe Benno Evers added a comment - https://reviews.apache.org/r/66815/
          alexr Alex R added a comment -
          commit 221884c88447f280dfa61cbbb465d9342f155f61
          Author:     Benno Evers <bevers@mesosphere.com>
          AuthorDate: Thu Dec 13 10:39:16 2018 +0100
          Commit:     Alexander Rukletsov <alexr@apache.org>
          CommitDate: Thu Dec 13 10:39:16 2018 +0100
          
              Removed an unconditional .get() in DefaultExecutor.
              
              This would fail in some cases where the optional
              message is `None`, e.g. when the container is in
              killing state.
              
              Review: https://reviews.apache.org/r/66815/
          
          alexr Alex R added a comment - commit 221884c88447f280dfa61cbbb465d9342f155f61 Author: Benno Evers <bevers@mesosphere.com> AuthorDate: Thu Dec 13 10:39:16 2018 +0100 Commit: Alexander Rukletsov <alexr@apache.org> CommitDate: Thu Dec 13 10:39:16 2018 +0100 Removed an unconditional .get() in DefaultExecutor. This would fail in some cases where the optional message is `None`, e.g. when the container is in killing state. Review: https://reviews.apache.org/r/66815/

          People

            bennoe Benno Evers
            abudnik Andrei Budnik
            Alex R Alex R
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: