Taken from scope

• Create infrastructure for analyzing the core dumps asynchronously.
  • AMI (found from task definition)
  • Binaires download link
  • Core dump download link
  • Debug symbols download link
  • Automatically trigger from the failed evergreen tasks and gather all of the needed inputs from the original evergreen task.
  • Outputs an “Hang Analyzer Output” zip file that could be uploaded to the hung evergreen task.
  • Run analysis on the same AMI that the original process was run on.
  • Make the new hang-analyzer results as discoverable as possible to users.
• We are heavily limited by evergreen here.
• The appendix has the proposed plan for making the results readily available to users.
  • In the current period when the core dumps and data files are uploaded, we generate a new task that will take the inputs and run analysis.
  • Allocates matching AMIs to generate backtraces.
  • Create appropriate logging and alerting on failure.
  • It is possible we might switch to a design in the alternatives section below if we run into issues with this method.
  • Inputs:
  • Requirements:
  • Generating a new task in the 15 minute period after a task timeout.