[SERVER-48036] Blacklist tests that look for "failpointMsg" on multiversion test suites. Created: 08/May/20  Updated: 28/May/20  Resolved: 14/May/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-43614 Consider adding "internal" message fi... Closed
Related
related to SERVER-48219 Fix multiversion tests which are fail... Closed
related to SERVER-43614 Consider adding "internal" message fi... Closed
Operating System: ALL
Sprint: Repl 2020-05-18
Participants:
Linked BF Score: 50

 Description   

Due to SERVER-43614, read_operations_during_step_down.js fails to find the "failpointMsg" field msg on the currentOp o/p printed by MongoDB 4.4



 Comments   
Comment by Suganthi Mani [ 14/May/20 ]

This is addressed by this git commit - https://github.com/mongodb/mongo/commit/6753c0a06c04dcb52ab2ebc4129f09f120fb1585. No work to be done for this ticket. So, closing it as dup of SERVER-43614.

Comment by Suganthi Mani [ 13/May/20 ]

Note: Any jstests that are using jstests/libs/curop_helpers.js and jstests/libs/pin_getmore_cursor.js will be impacted in multiversion suites because of SERVER-43614 change. Currently, we have 12 jstests (in replsets, sharding & core) multiversion suites that are affected because SERVER-43614 change

Comment by Jason Chan [ 08/May/20 ]

We should also blacklist verify_sessions_expiration_rs.js.

Comment by Suganthi Mani [ 08/May/20 ]

+ blacklist step_down_on_secondary.js

Comment by Lingzhi Deng [ 08/May/20 ]

We should also ban no_disconnect_on_stepdown.js which looks for failpointMsg as well.

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