Results Specification¶
On a machine that executed Avocado, job results are available under
[job-results]/job-[timestamp]-[short job ID]
, where logdir
is the
configured Avocado logs directory (see the data dir plugin), and the directory
name includes a timestamp, such as job-2021-09-28T14.21-e0775d9
. A typical
results directory structure can be seen below
$HOME/avocado/job-results/job-2021-09-28T14.21-e0775d9/
├── avocado.core.DEBUG
├── id
├── jobdata
│ ├── args.json
│ ├── cmdline
│ ├── config
│ ├── pwd
│ ├── test_references
│ └── variants-1.json
├── job.log
├── results.html
├── results.json
├── results.tap
├── results.xml
├── sysinfo
│ ├── post
│ │ ├── brctl show
│ │ ├── cmdline
│ │ ├── cpuinfo
│ │ ├── current_clocksource
│ │ ├── df -mP
│ │ ├── dmesg
│ │ ├── dmidecode
│ │ ├── fdisk -l
│ │ ├── gcc --version
│ │ ├── hostname
│ │ ├── ifconfig -a
│ │ ├── interrupts
│ │ ├── ip link
│ │ ├── journalctl.gz
│ │ ├── ld --version
│ │ ├── lscpu
│ │ ├── lspci -vvnn
│ │ ├── meminfo
│ │ ├── modules
│ │ ├── mounts
│ │ ├── numactl --hardware show
│ │ ├── partitions
│ │ ├── pci
│ │ ├── scaling_governor
│ │ ├── sched_features
│ │ ├── slabinfo
│ │ ├── uname -a
│ │ ├── uptime
│ │ └── version
│ ├── pre
│ │ ├── brctl show
│ │ ├── cmdline
│ │ ├── cpuinfo
│ │ ├── current_clocksource
│ │ ├── df -mP
│ │ ├── dmesg
│ │ ├── dmidecode
│ │ ├── fdisk -l
│ │ ├── gcc --version
│ │ ├── hostname
│ │ ├── ifconfig -a
│ │ ├── interrupts
│ │ ├── ip link
│ │ ├── ld --version
│ │ ├── lscpu
│ │ ├── lspci -vvnn
│ │ ├── meminfo
│ │ ├── modules
│ │ ├── mounts
│ │ ├── numactl --hardware show
│ │ ├── partitions
│ │ ├── pci
│ │ ├── scaling_governor
│ │ ├── sched_features
│ │ ├── slabinfo
│ │ ├── uname -a
│ │ ├── uptime
│ │ └── version
│ └── profile
└── test-results
├── 1-examples_tests_sleeptest.py_SleepTest.test
│ ├── debug.log
│ └── whiteboard
├── 2-examples_tests_sleeptest.py_SleepTest.test
│ ├── debug.log
│ └── whiteboard
└── 3-examples_tests_sleeptest.py_SleepTest.test
├── debug.log
└── whiteboard
From what you can see, the results directory has:
- A human readable
id
in the top level, with the job SHA1. - A human readable
job.log
in the top level, with human readable logs of the task - Subdirectory
jobdata
, that contains machine readable data about the job. - A machine readable
results.xml
andresults.json
in the top level, with a summary of the job information in xUnit/json format. - A top level
sysinfo
dir, with sub directoriespre
,post
andprofile
, that store sysinfo files pre/post/during job, respectively. - Subdirectory
test-results
, that contains a number of subdirectories (filesystem-friendly test ids). Those test ids represent instances of test execution results.
Test execution instances specification¶
The instances should have:
- A top level human readable
job.log
, with job debug information - A
sysinfo
subdirectory, with sub directoriespre
,post
andprofile
that store sysinfo files pre test, post test and profiling info while the test was running, respectively. - A
data
subdirectory, where the test can output a number of files if necessary.