In DEVPROD-5463 we found situations when build barons do not want failures from resmoke to be labeled as server crash severity types. The best mechanism for build baron to detect these failures is to read from failure metadata tags, which will be set based off the behavior of a failing resmoke test.

Request:

• when tasks are built with ASAN/AUBSAN/UBSAN/TSAN and the task fails due to a SIGQUIT/SIGABRT attach failure_metadata_tag NOT_SERVER_CRASH_SEVERITY . this appears to be due to the signal being delivered to the main thread rather than the signal handler
• if SIGABRT is sent by ( ? ) the hang analyzer the "NOT_SERVER_CRASH_SEVERITY" tag should be added in failure_metadata_tag. Sveta has provided some context on the behavior that should be ignored, hopefully this can surface a common place where this issue originates from:
  • CheckMetadataConsistencyInBackground hook logs Running hang analyzer for writeConcern timeout
  • a task times out with the message HIT EVERGREEN TIMEOUT: Hang analyzer will kill or abort processes
  • An assertion assert.soon failed in a test and there's a log message The hang analyzer is automatically called in assert.soon functions

CC:sviatlana.zuiko@mongodb.com