Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Storage Execution
Description
After triaging, reviewing, debugging, and interacting with several config fuzzer Hot BFs this week, here is a list of proposals from a few members of StoreEx on how to improve the config fuzzer so that a server engineer can find root causes of test failures quicker:
- WT string split to multiple lines
- Currently the WT config string is on one line which make diffing error-prone and time-consuming
- show defaults, min/max for each setting inline
- Configs can be surprising on first glance (a negative number?? must be a problem!)
- Showing some of this background can illuminate how extreme or unusual the fuzzed parameter is
- have fuzz seed be consistent across branches
- currently, a fuzz seed does not generate the same configs on all commits nor branches. This makes comparisons hard to carry out.
Attachments
Issue Links
- depends on
-
SERVER-70343 Make time series tests resilient to WCEs
-
- Open
-
- mentioned in
-
Page Loading...