[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] 4c9af1: gitlab-ci: Make more custom runner jo
[Qemu-commits] [qemu/qemu] 4c9af1: gitlab-ci: Make more custom runner jobs manual, an...
Tue, 14 Sep 2021 09:04:16 -0700
Author: Peter Maydell <firstname.lastname@example.org>
Date: 2021-09-14 (Tue, 14 Sep 2021)
gitlab-ci: Make more custom runner jobs manual, and don't allow failure
Currently we define a lot of jobs for our custom runners:
for both aarch64 and s390x we have
- clang (manual)
- notcg (manual)
This is overkill. The main reason to run on these hosts is to get
coverage for the host architecture; we can leave the handling of
differences like debug vs non-debug to the x86 CI jobs.
The jobs are also generally running OK; they occasionally fail due to
timeouts, which is likely because we're overloading the machine by
asking it to run 4 CI jobs at once plus the ad-hoc CI.
Remove the 'allow_failure' tag from all these jobs, and switch the
s390x-alldbg, aarch64-all, s390x-tci and aarch64-tci jobs to manual.
(We keep -all on s390x and -alldbg on aarch64 just for diversity
This will let us make the switch for s390x and aarch64 hosts from
the ad-hoc CI to gitlab.
Signed-off-by: Peter Maydell <email@example.com>
Reviewed-by: Willian Rampazzo <firstname.lastname@example.org>
Reviewed-by: Daniel P. Berrangé <email@example.com>
Acked-by: Thomas Huth <firstname.lastname@example.org>
|[Prev in Thread]
||[Next in Thread]|
- [Qemu-commits] [qemu/qemu] 4c9af1: gitlab-ci: Make more custom runner jobs manual, an...,
Peter Maydell <=