[SERVER-41103] Fix fuzzer task invocations Created: 12/May/19  Updated: 29/Oct/23  Resolved: 13/May/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.6.13, 4.0.10

Type: Bug Priority: Major - P3
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
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6
Sprint: STM 2019-05-20
Participants:
Linked BF Score: 0

 Description   

Update: the root of the problem is that SERVER-36530 was not backported to v4.0 or v3.6 so the fuzzer invocations look different on those branches vs master. The bug with dynamically generated fuzzer tasks is still valid but is not the final form of the problem.

The dynamically generate fuzzer task commands backport to v4.0 added an extra argument that exists only on master and not 4.0. This was caught in SERVER-40922 when the command line parsing library was upgraded to a newer version that no longer accepts duplicate arguments.



 Comments   
Comment by Githook User [ 12/May/19 ]

Author:

{'email': 'robertguo@me.com', 'name': 'Robert Guo', 'username': 'guoyr'}

Message: SERVER-41103 fix jstestfuzz_replication invocation
Branch: v3.6
https://github.com/mongodb/mongo/commit/e815c7ff680ba4687ed83a7a208d2daaef92e409

Comment by Githook User [ 12/May/19 ]

Author:

{'name': 'Robert Guo', 'username': 'guoyr', 'email': 'robertguo@me.com'}

Message: SERVER-41103 fix jstestfuzz invocation
Branch: v3.6
https://github.com/mongodb/mongo/commit/a89ad0c866e136357462b5a2436131b9e0efa5b8

Comment by Githook User [ 12/May/19 ]

Author:

{'name': 'Robert Guo', 'username': 'guoyr', 'email': 'robertguo@me.com'}

Message: SERVER-41103 fix jstestfuzz invocation
Branch: v4.0
https://github.com/mongodb/mongo/commit/7a97280b247bf9836aac4df6fd62754ca72f3894

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