[SERVER-48127] Do not pollute logs with expected assertion failure about waitForStepDownOnNonCommandShutdown Created: 12/May/20  Updated: 06/Dec/22  Resolved: 18/May/20

Status: Closed
Project: Core Server
Component/s: Logging, Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-48085 Suppress "unrecognized parameter wait... Closed
Assigned Teams:
Replication
Operating System: ALL
Participants:

 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.


Generated at Thu Feb 08 05:16:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.