From 2a206bfa59586404ad22ebe46535a5a64355c496 Mon Sep 17 00:00:00 2001 From: Gustavo Padovan Date: Wed, 3 Jul 2024 19:04:22 -0400 Subject: [PATCH] Update kernelci.org/content/en/labs/_index.md Co-authored-by: Chris Paterson --- kernelci.org/content/en/labs/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernelci.org/content/en/labs/_index.md b/kernelci.org/content/en/labs/_index.md index 3536bd55..5c507918 100644 --- a/kernelci.org/content/en/labs/_index.md +++ b/kernelci.org/content/en/labs/_index.md @@ -8,7 +8,7 @@ Anyone can connect their labs to KernelCI. Once a Lab is connected to KernelCI, It is up to each lab to define whether it will receive specific test configurations or a generic range of test jobs. If the lab is a LAVA lab, for example, the KernelCI [LAVA runtime](../api_pipeline/pipeline/connecting-lab) will generate test jobs for each single test that is configured to run. On the other hand, if a lab is implementing its own runtime (or bridge to Maestro APIs), they may choose to generate the individual test jobs themselves. -If are interesting it just sending the results of test runs in your infrastructure, you should look at sending the data to [KCIDB](../kcidb) - KernelCI common database for results. +If you are interested it just sending the results of test runs in your infrastructure, you should look at sending the data to [KCIDB](../kcidb) - KernelCI common database for results. There are a few ways labs can be connected to KernelCI. The documentation for connecting labs in the new architecture is evolving as we add labs.