[SERVER-83934] Remove jstestFuzz from running on debug variants Created: 06/Dec/23  Updated: 11/Dec/23  Resolved: 11/Dec/23

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

Type: Bug Priority: Major - P3
Reporter: Kruti Shah Assignee: Backlog - Cluster Scalability
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Cluster Scalability
Operating System: ALL
Participants:
Linked BF Score: 14

 Description   

jstestfuzz can trigger debug-only assertions (e.g. if (kDebugBuild) {crash();} )

that are expected for invalid input. We should stop running jstestfuzz on debug variants. The debug-only assertion specific to the bf attached is this one from the op_msg

This ticket is similar to what SERVER-68957 intended to do!



 Comments   
Comment by Louis Williams [ 11/Dec/23 ]

kruti.shah@mongodb.com, great, thanks for the update!

Comment by Kruti Shah [ 11/Dec/23 ]

louis.williams@mongodb.com After some consideration, I believe there is a less heavy-handed fix by altering the way testInternalTransactions handles the parsing of the commandInfo on invalid input. Going to mark this ticket as won't do. 

Comment by Louis Williams [ 06/Dec/23 ]

kruti.shah@mongodb.com, our debug assertions in the server are very valuable, especially when run in jstestfuzz. Can we find a less heavy-handed fix that doesn't involve removing test coverage? Can we consider how to not make the shell crash on invalid input?

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