User Tools

Site Tools


civilinfrastructureplatform:ciptesting:centalisedtesting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
civilinfrastructureplatform:ciptesting:centalisedtesting [2023/12/19 08:48]
swvanbuuren Add LAVA scheduler workflow with links
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 30: Line 30:
 The following schematic shows the workflow, that describes how test images are built and tested with LAVA. 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 |}}+{{:​civilinfrastructureplatform:​ciptesting:​cip-testing-6.1-workflow.png?800 |}}
  
 === Links === === Links ===
Line 83: 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 89: 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.1702975720.txt.gz · Last modified: 2023/12/19 08:48 by swvanbuuren