The armel/armhf targets have a lot in common. Instead of
testing both user/system emulation on each target, test
each one once. Mark the other combination optional, so
user can still run the tests manually.
We now test system-mode emulation on armel target, and
user-mode emulation to armhf target:
- armel-system Yes
- armel-user Optional
- armhf-system Optional
- armhf-user Yes
Signed-off-by: Philippe Mathieu-Daudé <phi...@redhat.com>
---
Cc: qemu-...@nongnu.org
Cc: Laurent Vivier <laur...@vivier.eu>
---
.gitlab-ci.d/crossbuilds.yml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml
index 03ebfabb3fa..e4526e98232 100644
--- a/.gitlab-ci.d/crossbuilds.yml
+++ b/.gitlab-ci.d/crossbuilds.yml
@@ -32,11 +32,17 @@ cross-armel-user:
<<: *cross_user_build_job_definition
variables:
IMAGE: debian-armel-cross
+ rules:
+ - when: manual
+ allow_failure: true
cross-armhf-system:
<<: *cross_system_build_job_definition
variables:
IMAGE: debian-armhf-cross
+ rules:
+ - when: manual
+ allow_failure: true
cross-armhf-user:
<<: *cross_user_build_job_definition
--
2.26.2
