-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Correctness
-
2024-10-15, 2024-10-29
-
0
Original slack thread: https://mongodb.slack.com/archives/CR8SNBY0N/p1726501072700799
In our benchmark suites, we silently dropped coverage for one benchmark because they use a pattern to define the binary. These patterns did not match any files and resmoke should have complained.
I think we do something similar for jstests already.