| Job ID | Actions | Submitter | Test Suite | Passes | Fails | Totals | Logged |
|---|---|---|---|---|---|---|---|
| 731 | agl-jenkins-user | lava | 33 | 0 | 33 | Oct. 8, 2018, 10:36 a.m. | |
| 731 | agl-jenkins-user | 0_can | 0 | 0 | 35 | Oct. 8, 2018, 10:36 a.m. | |
| 731 | agl-jenkins-user | 1_yocto-ptest | 0 | 0 | 1 | Oct. 8, 2018, 10:36 a.m. | |
| 731 | agl-jenkins-user | 2_busybox | 1 | 0 | 1 | Oct. 8, 2018, 10:36 a.m. | |
| 731 | agl-jenkins-user | 3_smoke-tests-basic | 5 | 0 | 5 | Oct. 8, 2018, 10:36 a.m. | |
| 731 | agl-jenkins-user | 4_service-check | 8 | 0 | 8 | Oct. 8, 2018, 10:36 a.m. |
The key is the name of the metadata named attribute which can be used in query conditions. Values relating to devices, device-types and URLs are formatted as links. Due to the variation between different git server interfaces, it is not possible to construct a full URL to the test definition file. The commit id of the test definition is part of the lava results for the job.
Inline test definitions which do not call lava-test-case will not record any
results and are shown in the metadata with the omitted prefix.
Attributes relating to items which can repeat within a single job include a number representing the sequence of that item within the job. For example, boot.0.method is the name of an attribute containing information on the first boot method used in the job. boot.0.commands would be an attribute containing information on the commands used by the first boot method in the job.
Metadata submitted as part of the job submission is also included, if present.