Currently, when joshua tests fail, the error output is not actionable. Users see "exit status 1" or raw XML traces without clear information about:
- Which specific test failed
- What random seed triggered the failure
- How to reproduce the failure locally
solution
Add a --verbose-errors flag to joshua tail that:
- Scans stored trace logs for error events (Severity >= 40)
- Extracts the
TestFile and RandomSeed from the trace
- Prints a formatted reproduction command alongside error details
Proposed behavior (joshua tail --verbose-errors):
[ERROR] Test: tests/fast/SimpleAtomicAdd.toml
Seed: 1424533409
Severity: 40
Error: Assertion failed in atomicOps.actor.cpp:142
Reproduce with:
./bin/fdbserver -r simulation -f tests/fast/SimpleAtomicAdd.toml -s 1424533409 -b on
Currently, when joshua tests fail, the error output is not actionable. Users see "exit status 1" or raw XML traces without clear information about:
solution
Add a
--verbose-errorsflag tojoshua tailthat:TestFileandRandomSeedfrom the traceProposed behavior (
joshua tail --verbose-errors):