[SERVER-24667] Explore running tests under Application Verifier's Cuzz Created: 20/Jun/16  Updated: 06/Dec/22

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

Type: Task Priority: Major - P3
Reporter: Mark Benvenuto Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Unresolved Votes: 0
Labels: stm, tig-evgconfig
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-24963 Concurrent collection.drop() and syst... Closed
Assigned Teams:
Server Tooling & Methods
Backwards Compatibility: Fully Compatible
Participants:

 Description   

From the Cuzz homepage, http://research.microsoft.com/en-us/projects/cuzz/

Cuzz is a very effective tool for finding concurrency bugs. Cuzz works on unmodified executables and is designed for maximizing concurrency coverage for your existing (unmodified) tests. It randomizes the thread schedules in a systematic and disciplined way, using an algorithm that provides probabilistic coverage guarantees.

Cuzz is very scalable and can run on large programs that create lots of threads. It is available as part of AppVerifier. You can find out more about Cuzz from this video or the paper below.

We should explore running our tests under Cuzz. While it will not detect race conditions ala CHESS or Thread Sanitizer it will instead simulate different program schedules which may help find bugs. This is Windows only.



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

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