The way test/format works is that it spits out a configuration file that is then used to (hopefully) reproduce a failure. It would be useful to capture the test/format configuration files that generate failures, and dedicate an Evergreen job to running just those config files.
Then we know that we are getting coverage of challenging configurations.
keith.bostic do you happen to have a stash of such configuration files?
- related to
WT-6744 Avoid duplication in test/format failure CONFIG set