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

Resmoke doesn't honor --continueOnFailure in ASAN builds

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.5
    • Affects Version/s: 3.1.4
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • ALL
    • Quint Iteration 5

      The issue is that resmokelib.errors.ServerFailure is considered fatal and converted into a StopExecution exception.

      Proposal is to raise a TestFailure instead of a ServerFailure when the mongod is found to exit with a nonzero code when being restarted.

      # Raise this after calling setup in case --continueOnFailure was specified.
      if not teardown_success:
          raise errors.ServerFailure("%s did not exit cleanly" % (self.fixture))
      

      The effect of this is that when LeakSanitizer causes the mongod to exit with code 23, we will mark the test that triggered the leak as having failed, but continue running the remaining tests.

            Assignee:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Reporter:
            jonathan.reams@mongodb.com Jonathan Reams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: