In WT-12997, the predictable replay format test failed. That Evergreen job runs test/format in RUNDIR.1. Then it copies it to RUNDIR.2 and RUNDIR.3. It runs in those directories with the same random data seed but a different random extra seed. The failure in WT-12997 resulted in debugger_t_9794.log and dump_t.9794.core in the top level cmake_build directory.

In the cmake_build/test/format directory there is RUNDIR.1, RUNDIR.2, RUNDIR.3

There is nothing obvious to help the developer investigating to know which database directory or format run goes with that log and core file. Going into the debugger on a spawn host and finding conn->home works but is too much effort for top-level triage.

This ticket should figure out some way to associate the core file name with the database directory it was using. Whether it is having format add a RUNDIR.N/PID file, or incorporating the directory name into the core file name, or having evergreen write all pid/test associations out into cmake_build, something standard to help the debugger would be good.