Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-87332

Investigate changing resmoke to use SIGABRT instead of SIGQUIT for {T/A}SAN variants

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Correctness

      The BB tooling incorrectly marks ASAN timeout BFs as server crashes because of the backtraces introduced by sending SIGQUIT to the mongo processes. We already had some logic to avoid counting these BFs as server crashes when SIGABRT is sent so we should try and unify this behavior.

            Assignee:
            Unassigned Unassigned
            Reporter:
            trevor.guidry@mongodb.com Trevor Guidry
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: