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

resmoke failures should self-document

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • TIG E (01/08/16), STM 2019-11-14, STM 2019-11-28
    • 2

    Description

      When resmoke fails, it should print out steps to help the user debug the failure. E.g. when resmoke detects that it's run in Evergreen, it should print out the places that the user should look for symptoms.

      Original description:
      At shutdown time, a fixture (Replication or Sharding) checks the return status of all the process shutdown procedures. If any of them have returned 'false' (which means that the process returned a non-0 exit status), it fails the test suite associated with that fixture.
      It would be helpful if the fixture wrote a message to the log stating which process caused the suite failure. Currently, the only way to diagnose this is to scour the logs looking for the exit status of each process; since we are looking for a line that is not "exited with code 0.", this is not a simple search to undertake.

      Attachments

        Activity

          People

            carl.worley@mongodb.com Raiden Worley (Inactive)
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: