On 26/04/2024 14.30, Peter Maydell wrote:
On Fri, 26 Apr 2024 at 12:38, Thomas Huth <th...@redhat.com> wrote:

During the past months, the netbsd and openbsd jobs in the Cirrus-CI
were broken most of the time - the setup to run a BSD in KVM on Cirrus-CI
from gitlab via the cirrus-run script was very fragile, and since the
jobs were not run by default, it used to bitrot very fast.

Now Cirrus-CI also introduce a limit on the amount of free CI minutes
that you get there, so it is not appealing at all anymore to run
these BSDs in this setup - it's better to run the checks locally via
"make vm-build-openbsd" and "make vm-build-netbsd" instead. Thus let's
remove these CI jobs now.

So what's the plan to keep BSD CI coverage? This seems
like a step backwards towards "the person handling the
pullreq merges has to do some local private ad-hoc testing
too" :-(

With regards to NetBSD and OpenBSD, this is not a step backward since these gitlab jobs were never run anyway (they could only be triggered manually, but hardly anybody did that AFAIK).

If we want to have proper support for those OSes, I think somebody would need to set up a custom runner on a beefy KVM-capable server somewhere where we could run the "make vm-build-*bsd" commands. By the way, are Eldon's CI runners still around? IIRC they were capable of running KVM ?

 Thomas



Reply via email to