[SERVER-35389] Remove dead code from old FSM suite Created: 04/Jun/18  Updated: 29/Oct/23  Resolved: 08/Jun/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 4.0.0-rc0
Fix Version/s: 4.0.1

Type: Task Priority: Minor - P4
Reporter: Robert Guo (Inactive) Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: TIG 2018-06-18
Participants:
Linked BF Score: 0

 Description   

With SERVER-29999, all FSM suites have moved to remoke fixtures, we should do some clean up work to remove dead code. To not introduce risk areas, we should not modify any code, and just remove the fsm_all*.js JS runners as well as any dead code that a JS static analyzer finds in the fsm_libs directory.



 Comments   
Comment by Githook User [ 06/Jul/18 ]

Author:

{'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}

Message: SERVER-35389 remove dead code from FSM suite
Branch: v4.0
https://github.com/mongodb/mongo/commit/57676955465bbf6bdfbcc7e663465f2550f4e54e

Comment by Githook User [ 05/Jul/18 ]

Author:

{'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}

Message: SERVER-35389 remove dead code from FSM suite

(cherry picked from commit fe841d1b78f4d03bd8fbc534a2b9ea42abb02190)
Branch: v4.0
https://github.com/mongodb/mongo/commit/341b07514f41f6126b671d93a8c205349f501510

Comment by Githook User [ 08/Jun/18 ]

Author:

{'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}

Message: SERVER-35389 remove dead code from FSM suite
Branch: master
https://github.com/mongodb/mongo/commit/fe841d1b78f4d03bd8fbc534a2b9ea42abb02190

Comment by Max Hirschhorn [ 04/Jun/18 ]

as well as any dead code that a JS static analyzer finds in the fsm_libs directory

I don't think we should remove anything from jstests/concurrency/fsm_libs/runner.js. It should be possible to write new instances of runWorkloadsSerially() and runWorkloadsInParallel() akin to what the jstests/noPassthrough/backup_restore*.js tests do.

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