[SERVER-26730] Rewrite currentop.js to use the setYieldAllLocksHang failpoint Created: 21/Oct/16  Updated: 06/Dec/16  Resolved: 05/Dec/16

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

Type: Improvement Priority: Major - P3
Reporter: Charlie Swanson Assignee: Charlie Swanson
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-27042 Fix and modernize currentop.js Closed
Sprint: Query 2016-11-21, Query 2016-12-12
Participants:

 Description   

This test occasionally fails due to timing on slow machines. We can instead use the setYieldAllLocksHang failpoint to remove any timing-related flakiness.



 Comments   
Comment by Charlie Swanson [ 05/Dec/16 ]

As discussed as part of SERVER-27042, the setYieldAllLocksHang failpoint is not appropriate for this test, since we are specifically asserting on the locks portion of the currentop output. I'm closing this as a duplicate of SERVER-27042, since that fix will accomplish the same goal of making this test less flaky.

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