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

Do not pollute logs with expected assertion failure about waitForStepDownOnNonCommandShutdown

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Replication
    • ALL

    Description

      Logs from JS tests are polluted with an assertion failure regarding the missing parameter waitForStepDownOnNonCommandShutdown. This parameter is expected to be missing before 4.1.10 and after 4.4 and it will be definetly dropped by SERVER-47797 once 4.6 it will became last-stable.

      Until then we don't want this assertion to pollute our logs. Moreover many auto generated BFG suggest this assertion as a possible cause of the problem and obviously it is not. This makes the life of the build baron much more difficult.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: