From: Jan Kiszka <[email protected]> We currently have only one instance per board in our lab, and there is only one QEMU instance max, independently of the architecture. So far, test jobs requesting the same one can start in parallel and will then wait on the LAVA cli, consuming job time. Avoid this at CI level already.
Signed-off-by: Jan Kiszka <[email protected]> --- Changes in v2: - put all QEMUs into one group (misunderstanding of mine...) ci/gitlab-ci-base.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ci/gitlab-ci-base.yml b/ci/gitlab-ci-base.yml index 53ae66b..28c383c 100644 --- a/ci/gitlab-ci-base.yml +++ b/ci/gitlab-ci-base.yml @@ -47,6 +47,7 @@ default: .lava-test:qemu-amd64: extends: .test + resource_group: board-qemu variables: TARGET: qemu-amd64 @@ -58,6 +59,7 @@ default: .lava-test:qemu-armhf: extends: .test + resource_group: board-qemu variables: TARGET: qemu-armhf @@ -69,6 +71,7 @@ default: .lava-test:qemu-arm64: extends: .test + resource_group: board-qemu variables: TARGET: qemu-arm64 @@ -80,6 +83,7 @@ default: .lava-test:board-hikey: extends: .test + resource_group: board-hikey variables: TARGET: hikey @@ -91,6 +95,7 @@ default: .lava-test:board-beagle-bone-black: extends: .test + resource_group: board-beagle-bone-black variables: TARGET: beagle-bone-black @@ -102,5 +107,6 @@ default: .lava-test:board-x86-64-efi: extends: .test + resource_group: board-x86-64-efi variables: TARGET: x86-64-efi -- 2.26.2
