[SERVER-48219] Fix multiversion tests which are failing as a result of SERVER-43614 Created: 14/May/20  Updated: 29/Oct/23  Resolved: 11/Jun/20

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

Type: Task Priority: Major - P3
Reporter: Bernard Gorman Assignee: Bernard Gorman
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-48036 Blacklist tests that look for "failpo... Closed
is related to SERVER-29030 Announce new primary via heartbeat re... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2020-06-01, Query 2020-06-15
Participants:

 Description   

In SERVER-43614 we introduced a new failpointMsg field in currentOp output, intended to replace the user-visible msg field for internal use by tests that must wait for an operation to hit a particular failpoint. However, this caused tests to begin failing in multiversion suites because the last-stable members of the replica set never produce a field called failpointMsg.

We should update jstests/libs/curop_helpers.js to look for both field names in currentOp output, and un-blacklist the tests blacklisted under SERVER-48036.



 Comments   
Comment by Githook User [ 11/Jun/20 ]

Author:

{'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}

Message: SERVER-48219 Fix multiversion tests which are failing after introducing the failpointMsg field
Branch: master
https://github.com/mongodb/mongo/commit/33d4a16dec74c49d05eefacf2d965fab23073195

Comment by Nicholas Zolnierz [ 01/Jun/20 ]

+ jstests/sharding/kill_pinned_cursor.js, started using the helper as part of SERVER-48502

Comment by Suganthi Mani [ 14/May/20 ]

+ jstests/libs/pin_getmore_cursor.js to look for both field names in currentOp output.

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