Major - P3 In failure logs we can see this:
[2022/07/28 05:38:12.687] # Parse through any failures inside the WT_TEST directory. [2022/07/28 05:38:12.687] venv/bin/python3 ../test/evergreen/print_stack_trace.py --unit_test -e venv/bin/python3 -c WT_TEST -l . [2022/07/28 05:38:12.725] # Look through the stress format directory for any coredumps. [2022/07/28 05:38:12.725] cd test/format [2022/07/28 05:38:12.725] venv/bin/python3 ../../../test/evergreen/print_stack_trace.py --format -e ./t -c . -l . [2022/07/28 05:38:12.725] sh: 8: venv/bin/python3: not found [2022/07/28 05:38:12.725] Command failed: shell script encountered problem: exit code 127 [2022/07/28 05:38:12.725] Finished 'shell.exec' in "dump stacktraces" in 39.332326ms
Notice the venv/bin/python3 not found. If we have a relative path for python, then we can't "cd" to a different directory. The print_stack_trace.py script has a -c option to set the directory, that should be used instead of cd test/format .
Or maybe use a full pathname for the venv python. Or use both approaches together.