[SERVER-49763] Add jstestfuzz suites to run against last-continuous release Created: 21/Jul/20  Updated: 29/Oct/23  Resolved: 26/Oct/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Task Priority: Major - P3
Reporter: Jason Chan Assignee: Mikhail Shchatko
Resolution: Fixed Votes: 0
Labels: tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: STM 2021-11-01
Participants:
Story Points: 2

 Description   

Currently, for each of the fuzzers that run against the last-stable versions, we should add a new task that runs against the last-continuous version.

Suggestion from STM: Pass in the old version (either last-lts or last-continuous) as an argument into npm jstestfuzz to determine what tasks to generate.



 Comments   
Comment by Githook User [ 26/Oct/21 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}

Message: SERVER-49763 Run fuzzers against last-continuous and last-lts
Branch: master
https://github.com/mongodb/mongo/commit/a62bc5316de00b706e1308ed35a98f597b89f2dc

Comment by Githook User [ 26/Oct/21 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}

Message: SERVER-49763 Use 'useRandomBinVersionsWithinReplicaSet' to determine the old version (#572)
Branch: master
https://github.com/10gen/jstestfuzz/commit/ab83d00f41bae509f62adaa65dce753bc325f62e

Comment by Brooke Miller [ 24/May/21 ]

Changing this to be 5.1 Required as I don't believe this is actually needed for 5.0, since we're aiming to get this project completed prior to 5.1 rc0 in August.

However, please correct me if I am wrong, jason.chan or robert.guo.

Comment by Lingzhi Deng [ 12/Aug/20 ]

Talked to robert.guo and we agreed that this is better aligned with PM-1803. Assigning to STM team.

Generated at Thu Feb 08 05:20:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.