-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Test Format
-
None
-
Storage Engines - Persistence
-
846.134
-
None
-
None
Currently, format.sh captures each job's WiredTiger output to a per-job log file, but discards it once the job resolves - in resolve(), both the "successful job" path and the "killed job" path unconditionally rm -rf $dir $log $rec_dir. Failed jobs already keep their log via report_failure(), but successful and timed-out/killed jobs don't and the deleted log is the only record of what that specific job was doing when it got killed.
Additionally, test format only reports to its own stdout when a job finishes, so a single-long running job is indistinguishable from a hang, and long-running jobs (>= 2 hrs) are killed when nothing is printed to stdout/stderr.
Fix: retain the job's log, CONFIG, and WiredTigerStat.* files, and add live logging from WT to stdout/stderr.
- is related to
-
WT-18400 Expose the top consumers of cache memory (update and total bytes) on a live connection
-
- Closed
-
-
WT-18008 [Verify] race-condition-stress-asan-test-3 timeout: possible stall in new HS verify logic (__verify_key_hs) under ASAN
-
- Closed
-
- related to
-
WT-18735 Unexpected garbled characters appear in test/format run logs
-
- Closed
-