[SERVER-8342] Delete old query_yield tests Created: 25/Jan/13  Updated: 05/Aug/19  Resolved: 05/Aug/19

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: 2.3.2
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: Sam Mercier
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-8579 Consolidate Mongod Lock/Resource Sche... Closed
is related to SERVER-9675 query_yield1.js failing on Windows 64... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2019-06-17, Query 2019-07-01, Query 2019-07-15, Query 2019-07-29, Query 2019-08-12
Participants:

 Description   

The query_yield tests (query_yield1.js, query_yield2.js) were disabled during the 2.5 cycle due to lock scheduler issues. When we complete work on our new locking system, let's re-enable these tests.

Tests were disabled to resolve SERVER-9675.



 Comments   
Comment by Githook User [ 01/Aug/19 ]

Author:

{'name': 'samontea', 'email': 'merciers.merciers@gmail.com', 'username': 'samontea'}

Message: SERVER-8342 Delete old query_yield tests
Branch: master
https://github.com/mongodb/mongo/commit/9e60c8c7889b8d8d11335e28d0107d62ddf004f8

Comment by Eric Milkie [ 20/Apr/18 ]

These query yielding tests were not written in non-flaky way, and we have since added better coverage. I recommend we delete these files.

Comment by Matt Kangas [ 12/Jul/13 ]

Deactivated query_yield1.js and query_yield2.js in rev 15333b2a308 for 2.5.1 release to clear buildbot failures on non-Linux platforms.

NEED to reactivate them when we actually revisit lock scheduler fairness, e.g. SERVER-8579

Generated at Thu Feb 08 03:17:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.