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
Next revision Both sides next revision
civilinfrastructureplatform:ciptesting:centalisedtesting [2019/08/07 15:03]
patersonc [CIP Centralised Testing]
civilinfrastructureplatform:ciptesting:centalisedtesting [2023/12/18 12:18]
swvanbuuren Add section on SQUAD test reporting
Line 4: Line 4:
 The second goal for CIP testing was to centralise testing so that developers can run tests without having local access to a platform. This is becoming more and more useful for CIP as the list of [[civilinfrastructureplatform:​ciptesting:​cipreferencehardware|reference platforms]] grows. It also means that tests can be triggered and run automatically 24/7. The second goal for CIP testing was to centralise testing so that developers can run tests without having local access to a platform. This is becoming more and more useful for CIP as the list of [[civilinfrastructureplatform:​ciptesting:​cipreferencehardware|reference platforms]] grows. It also means that tests can be triggered and run automatically 24/7.
  
-The third goal for CIP testing ​is 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]].
 ===== 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 27: Line 29:
 A LAVA worker (or lab) manages target (virtual/​physical hardware) control. There can be one or many different LAVA workers. A LAVA worker (or lab) manages target (virtual/​physical hardware) control. There can be one or many different LAVA workers.
  
-Currently CIP has one LAVA worker (lab-cip-renesas) based in the Renesas UK officeTargets ​attached ​to the worker ​can be viewed on the [[https://​lava.ciplatform.org/​scheduler/​worker/​lab-cip-renesas|master ​website]].+Currently CIP has three LAVA workersA summary of all of the attached ​targets ​can be viewed on the [[https://​lava.ciplatform.org/​scheduler/​alldevices|LAVA master]].
  
 CIP encourage as many LAVA workers to be set up as possible and have provided a [[https://​gitlab.com/​cip-project/​cip-testing/​lava-docker/​blob/​cip-lava-docker/​documentation/​setup_cip_lava_lab.md|guide]] on how to do this.  CIP encourage as many LAVA workers to be set up as possible and have provided a [[https://​gitlab.com/​cip-project/​cip-testing/​lava-docker/​blob/​cip-lava-docker/​documentation/​setup_cip_lava_lab.md|guide]] on how to do this. 
  
 === Links === === Links ===
-  * lab-cip-renesas:​ https://​lava.ciplatform.org/​scheduler/​worker/​lab-cip-renesas+  ​* lab-cip-cybertrust:​ [[https://​lava.ciplatform.org/​scheduler/​worker/​lab-cip-cybertrust]] 
 +  * lab-cip-mentor:​ [[https://​lava.ciplatform.org/​scheduler/​worker/​lab-cip-mentor]] 
 +  ​* lab-cip-renesas: ​[[https://​lava.ciplatform.org/​scheduler/​worker/​lab-cip-renesas]]
   * CIP worker setup guide: https://​gitlab.com/​cip-project/​cip-testing/​lava-docker/​blob/​cip-lava-docker/​documentation/​setup_cip_lava_lab.md   * CIP worker setup guide: https://​gitlab.com/​cip-project/​cip-testing/​lava-docker/​blob/​cip-lava-docker/​documentation/​setup_cip_lava_lab.md
  
Line 56: Line 60:
 KernelCI is a widely used project that aims to unify all upstream Linux kernel testing efforts in order to provide a single place where to store, view, compare and track these results. KernelCI is a widely used project that aims to unify all upstream Linux kernel testing efforts in order to provide a single place where to store, view, compare and track these results.
  
-At the moment ​CIP has their own instance of the [[https://kernelci.ciplatform.org/|KernelCI website]] where test results ​can be tracked.+CIP plans to submit our test results to kernelci.org ​so that they can be viewed by all.
  
 == Mailing list == == Mailing list ==
Line 62: Line 66:
  
 LAVA can also email any email address specified in the job description. LAVA can also email any email address specified in the job description.
 +
 +== 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]].
  
 === Links === === Links ===
Line 123: Line 131:
 === Links === === Links ===
   * Mainline Linux Kernel: https://​git.kernel.org/​pub/​scm/​linux/​kernel/​git/​torvalds/​linux.git   * Mainline Linux Kernel: https://​git.kernel.org/​pub/​scm/​linux/​kernel/​git/​torvalds/​linux.git
-  * LTS Kernel repository: https://​git.kernel.org/​pub/​scm/​linux/​kernel/​git/​stable/​linux.git+  * Stable ​Kernel repository: https://​git.kernel.org/​pub/​scm/​linux/​kernel/​git/​stable/​linux.git 
 +  * Stable Kernel release candidate repository: https://​git.kernel.org/​pub/​scm/​linux/​kernel/​git/​stable/​linux-stable-rc.git/​
   * Real Time Kernel repository: https://​git.kernel.org/​pub/​scm/​linux/​kernel/​git/​rt/​linux-rt-devel.git   * Real Time Kernel repository: https://​git.kernel.org/​pub/​scm/​linux/​kernel/​git/​rt/​linux-rt-devel.git
  
civilinfrastructureplatform/ciptesting/centalisedtesting.txt · Last modified: 2023/12/19 08:55 by swvanbuuren