[SERVER-73485] Remove jstests/parallel/basic* Created: 31/Jan/23  Updated: 29/Oct/23  Resolved: 25/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Dan Larkin-York
Resolution: Fixed Votes: 1
Labels: techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-39362 Make parallel/basic.js test respect r... Closed
Related
related to SERVER-73035 Use larger instance when running para... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: Execution NAMR Team 2023-09-04
Participants:
Linked BF Score: 2

 Description   

The parallel tests have become rather noisy. A significant portion (up to 87%) of the BFs generated involving these tests end up requiring test-only fixes rather than actual server issues. Most of our parallel testing has moved to the concurrency suites, so it's not clear that these tests are providing enough value relative to the cost to maintain them.



 Comments   
Comment by Githook User [ 25/Aug/23 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-73485 Remove jstests/parallel/basic* and associated dead code
Branch: master
https://github.com/mongodb/mongo/commit/456f73fc1f444467f515838d963124617f63b241

Comment by Anton Korshunov [ 07/Feb/23 ]

max.hirschhorn@mongodb.com Parallel testing was not required to reproduce the bug described in SERVER-65814. It was a coincidence that while doing parallel testing we created a plan cache entry with certain properties which we were able to reuse in another test, but due to a programming error the second test would blow up. It's interesting that we didn't create a standalone test for this issue, perhaps the thinking was that we had several BFs in the parallel suite with the same symptom and existing test coverage would be enough.

Similarly, parallel testing wasn't required to cause or reproduce the bug described in SERVER-65897, and an existing test was extended to cover this scenario.

I can't say that we were heavily relying on the parallel suite to test the SBE plan cache, but it was definitely of some interest for us, and luckily we revealed a couple real issues which otherwise could be caught only by the fuzzer. However, I tend to agree that all parallel testing should be planned, designed and implemented using the concurrency suites and be based on well-thought scenarios rather than on randomness and sheer luck (for that we have the fuzzer).

Generated at Thu Feb 08 06:24:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.