Testing/LAVA: Difference between revisions
m (moved LAVA to Testing/LAVA) |
No edit summary |
||
| Line 4: | Line 4: | ||
The master QEMU git tree is monitored by a job [https://ci.linaro.org/jenkins/job/qemu-mainline/] on Linaro's CI server. When an update to the branch is detected a number of jobs are spawned from it. The LAVA based results are visible in the [https://validation.linaro.org/dashboard/streams/anonymous/qemu-master/bundles/ qemu-master result stream]. | The master QEMU git tree is monitored by a job [https://ci.linaro.org/jenkins/job/qemu-mainline/] on Linaro's CI server. When an update to the branch is detected a number of jobs are spawned from it. The LAVA based results are visible in the [https://validation.linaro.org/dashboard/streams/anonymous/qemu-master/bundles/ qemu-master result stream]. | ||
Revision as of 09:23, 12 October 2016
LAVA is Linaro's Automated Validation test suite [1]. In QEMU's context a number of CI job have been set-up to track the status of ARMv7 and ARMv8 support in QEMU. While the validatation.linaro.org server is focused on ARM related things LAVA itself is platform independent.
Implementation Details
The master QEMU git tree is monitored by a job [2] on Linaro's CI server. When an update to the branch is detected a number of jobs are spawned from it. The LAVA based results are visible in the qemu-master result stream.