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

Log a message in MongoRunner.stopMongod() when allowedExitCodes is used to test intentional abort

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.4.1
    • Fix Version/s: 3.5.9
    • Component/s: Testing Infrastructure
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      TIG 2017-04-17, TIG 2017-05-08, TIG 2017-05-29, TIG 2017-06-19
    • Linked BF Score:
      0

      Description

      Some tests intentionally cause the server to abort (e.g. fatal assertion). When quickly scanning the log output for a reason as to why the test failed, Server team engineers are misled by backtraces appearing in the output. We should write a message in MongoRunner.stopMongod() when the allowedExitCodes option is being used to test for an intentional abort.

      Original description

      Some tests intentionally cause the server to fassert. When diagnosing a test failure, people are sometimes thrown off by seeing fassert backtraces in the logs for fasserts that are expected. If we create a server option to suppress backtraces for fasserts with certain codes, then the test use this option to prevent expected fasserts from appearing in the logs.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              robert.guo Robert Guo
              Reporter:
              tess.avitabile Tess Avitabile
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: