On 28/08/2020 11.54, Thomas Huth wrote: > On 28/08/2020 10.59, Daniel P. Berrangé wrote: >> On Mon, Aug 24, 2020 at 11:44:10AM +0200, Thomas Huth wrote: >>> The FreeBSD jobs currently hit the 1h time limit in the Cirrus-CI. >>> We've got to exclude some build targets here to make sure that the job >>> finishes in time again. The targets that are excluded should not hurt >>> much, since e.g. all the code from i386-softmmu is covered again by >>> x86_64-softmmu. >>> >>> Signed-off-by: Thomas Huth <th...@redhat.com> >>> --- >>> Not sure why the FreeBSD builds suddenly got slower and hit the 1h >>> time limit now. Looking at https://cirrus-ci.com/github/qemu/qemu >>> it seems like the FreeBSD jobs were already taking ca. 48 minutes >>> since quite a while, but since the Meson build system has been merged, >>> they now always hit the 1h limit. Could it be that Meson is slow on >>> FreeBSD? >>> >>> I hope disabling some of the "redundant" targets is ok for everybody >>> to get this working again. Alternatively, we could also introduce a >>> second FreeBSD job and run half of the targets in one job, and half >>> of the targets in the other job if that's preferred? >> >> I'd probably suggest we go for two jobs, as there doesn't look like >> any constraint on running multiple jobs that we'll hit any time >> soon. > > I gave it a try, but either I'm doing something wrong, or it is not > possible to run multiple FreeBSD tasks on cirrus-ci for one commit
I apparently needed a weekend in between to get a clean head again. I was doing indeed something wrong... apparently you have to name your tasks on cirrus-ci with "_task" at the end. If you use "_task1" and "_task2", it does now work anymore. Sigh. So I'll try to cook a proper patch to split the job instead. Thomas
