civilinfrastructureplatform:ciptesting:centalisedtesting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
civilinfrastructureplatform:ciptesting:centalisedtesting [2023/12/18 12:18] swvanbuuren Add section on SQUAD test reporting |
civilinfrastructureplatform:ciptesting:centalisedtesting [2025/06/03 13:41] (current) patersonc [CIP Centralised Testing] Updated KernelCI dashboard link |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| The third goal for CIP testing was to set up Continuous Integration (CI) testing to automatically test CIP software on CIP hardware. See the [[civilinfrastructureplatform:ciptesting:centalisedtesting:cioverview|Continuous Integration testing overview]] page for more details. | The third goal for CIP testing was to set up Continuous Integration (CI) testing to automatically test CIP software on CIP hardware. See the [[civilinfrastructureplatform:ciptesting:centalisedtesting:cioverview|Continuous Integration testing overview]] page for more details. | ||
| - | The fourth goal for CIP testing is to integrate with the [[https://kernelci.org/|KernelCI project]]. This work is underway and the latest results can be viewed at [[https://kernelci.ciplatform.org/|kernelci.ciplatform.org]]. | + | The fourth goal for CIP testing is to integrate with the [[https://kernelci.org/|KernelCI project]]. This work is underway and the latest results can be viewed at [[https://dashboard.kernelci.org/tree?i=30&ts=cip|dashboard.kernelci.org]]. |
| ===== CIP Testing Architecture ===== | ===== CIP Testing Architecture ===== | ||
| The block diagram below provides an overview of CIP's centralised test infrastructure. | The block diagram below provides an overview of CIP's centralised test infrastructure. | ||
| Line 16: | Line 16: | ||
| This schedules submitted test jobs to run on available hardware targets. | This schedules submitted test jobs to run on available hardware targets. | ||
| - | CIP have set up their own instance of LAVA (Linaro Automated Validation Architecture). LAVA is a continuous integration system for deploying operating systems onto physical and virtual hardware for running tests. See the [[https://www.lavasoftware.org/|LAVA website]] for more details. | + | CIP has set up their own instance of LAVA (Linaro Automated Validation Architecture). LAVA is a continuous integration system for deploying operating systems onto physical and virtual hardware for running tests. See the [[https://www.lavasoftware.org/|LAVA website]] for more details. |
| - | CIP are using a version of LAVA maintained by the [[https://kernelci.org/|KernelCI project]] which [[https://github.com/kernelci/lava-docker/|containerises]] support in a Docker image. | + | CIP is using a version of LAVA maintained by the [[https://kernelci.org/|KernelCI project]] which [[https://github.com/kernelci/lava-docker/|containerises]] support in a Docker image. |
| === Links === | === Links === | ||
| Line 25: | Line 25: | ||
| * cip-lava-docker source code: https://gitlab.com/cip-project/cip-testing/lava-docker | * cip-lava-docker source code: https://gitlab.com/cip-project/cip-testing/lava-docker | ||
| * How to submit a LAVA test job: [[civilinfrastructureplatform:ciptesting:centalisedtesting:submittinglavajobs|Submitting a LAVA test job]] | * How to submit a LAVA test job: [[civilinfrastructureplatform:ciptesting:centalisedtesting:submittinglavajobs|Submitting a LAVA test job]] | ||
| + | |||
| + | ==== Test scheduler workflow ==== | ||
| + | |||
| + | The following schematic shows the workflow, that describes how test images are built and tested with LAVA. | ||
| + | |||
| + | {{:civilinfrastructureplatform:ciptesting:cip-testing-6.1-workflow.png?800 |}} | ||
| + | |||
| + | === Links === | ||
| + | |||
| + | * CIP Testing group: https://gitlab.com/cip-project/cip-testing | ||
| + | * [[https://gitlab.com/cip-project/cip-testing/linux-cip-ci|linux-cip-ci]] | ||
| + | * [[https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines|linux-cip-pipelines]] | ||
| + | * CIP Kernel group: https://gitlab.com/cip-project/cip-kernel | ||
| + | * [[https://gitlab.com/cip-project/cip-kernel/linux-cip|linux-cip]] | ||
| ==== Target Control ==== | ==== Target Control ==== | ||
| Line 69: | Line 83: | ||
| == SQUAD == | == SQUAD == | ||
| - | For detailed test reporting CIP uses the Software Quality Dashboard (SQUAD). Build success and test results are reported to the [[https://squad.ciplatform.org/|CIP SQUAD instance]]. | + | For detailed test reporting CIP uses the Software Quality Dashboard (SQUAD). Build success and test results are reported to the [[https://squad.ciplatform.org/|CIP SQUAD]]. |
| + | |||
| + | The following diagram shows how build results are reported to SQUAD and test jobs are submitted to LAVA and monitored by SQUAD. | ||
| + | |||
| + | {{:civilinfrastructureplatform:ciptesting:cip-testing-with-squad.png?400|}} | ||
| === Links === | === Links === | ||
| Line 75: | Line 93: | ||
| * CIP KernelCI instance: https://kernelci.ciplatform.org | * CIP KernelCI instance: https://kernelci.ciplatform.org | ||
| * CIP test results mailing list: https://lists.cip-project.org/mailman/listinfo/cip-testing-results | * CIP test results mailing list: https://lists.cip-project.org/mailman/listinfo/cip-testing-results | ||
| + | * CIP SQUAD Reporting: https://squad.ciplatform.org/ | ||
| ==== Artifact Storage ==== | ==== Artifact Storage ==== | ||
civilinfrastructureplatform/ciptesting/centalisedtesting.1702901921.txt.gz · Last modified: 2023/12/18 12:18 by swvanbuuren
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
