[SERVER-57730] Resmoke.py should bisect non-multiversion fuzzer test failures for 5.0 and above Created: 15/Jun/21  Updated: 27/Oct/23  Resolved: 20/Aug/21

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

Type: Task Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Siran Wang (Inactive)
Resolution: Gone away Votes: 1
Labels: dp-qp-stakeholder-request-2021-07
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-53951 Add a mode to resmoke to bisect changes Closed
Issue split
split to SERVER-59449 Add resmoke.py `bisect` command Closed
split to SERVER-59451 Evergreen-aware bisect Closed
split to SERVER-59452 Setup and call resmoke.py for each bi... Closed
Sprint: STM 2021-09-06
Participants:

 Description   

Allow deterministic non-multiversion fuzzer failures to be bisected for all commits on master since 5.0 branching.

 

Design sketch:

  • Write a binary search function on git history that simulates git bisect but takes into account where binaries are available for download and update the bisection point.
  • Using the bisection point from above, use multiversion setup to download the artifacts, binaries, and virtualenv (if available) into the build/ directory and run resmoke there
  • Call multiversion setup to download binaries and return the binary commit
  • Allow passing in additional arguments through the command line (e.g. if someone wants to run a single file)


 Comments   
Comment by Charlie Swanson [ 10/May/22 ]

Excellent, thank you!

Comment by Tausif Rahman (Inactive) [ 10/May/22 ]

charlie.swanson@mongodb.com the bisect command got moved to db-contrib-tool (https://github.com/10gen/db-contrib-tool).
Once you have db-contrib-tool installed you can run the following command which explains usage & how the bisect is performed.

db-contrib-tool bisect --help

Comment by Charlie Swanson [ 10/May/22 ]

brooke.miller@mongodb.com  siran.wang@mongodb.com robert.guo@mongodb.com tausif.rahman@mongodb.com is there documentation for this anywhere? I see the three linked tickets are finished and I don't know how to use it  

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