- Work Dir
-
Yath work directory layout
This is what a work dir looks like:
- UUID/
- Each represent a job (test file that was run)
- PID
- will contain the pid of the root process for the test job
- complete
- will be present when the run is complete
- error.log
- contains any STDERR generated within yath itself
- output.log
- contains any STDOUT generated within yath itself
- jobs.jsonl
- is a list of jobs that have been started already
- queue.jsonl
- contains the full list of jobs that were to be run
- ready
- is used internally
- run.json
- contains details and configuration for the run
- Job Dir
-
Yath job directory layout
- tmp/
- Job temp dir, $TMPDIR is set to this
- exit
- Present when the job is complete, contaisn the exit code of the main process
- file
- Contains path/to/the/test/file.t
- start
- Timestamp of the job starting
- stdout
- Contains all the stdout generated by the test file
- stderr
- Contains all stderr generated by the test file
- stdin
- Contains any stdin text that was passed into the test file
Note that in most cases stderr and stdout will both contain special
syncronization lines used to make sure STDOUT, STDERR, and test events
can be sorted into the proper order. Yath does not normally show these
sync point in output.
The events/ dir contains 1 file for each process and/or thread started
by the test job. These files contain all the Test2 event data for that
process/thread.