On 11/07/2024 2:09 pm, Anthony PERARD wrote:
> On Thu, Jul 11, 2024 at 12:15:07PM +0100, Andrew Cooper wrote:
>> Randconfig builds pick CONFIG_DEBUG with 50% probability. Therefore
>> $foo{,-debug}-randconfig are two identical jobs with misleading names.
>>
>> Furthermore, arm64 has a randconfig jobs for both the alpine and bookworm
>> build environments. Both use GCC 12.2, so we have 4 identical jobs. Delete
>> 3
>> of them.
>>
>> This leaves us with 4 primary randconfig jobs:
>>
>> gitlab-ci/build.yaml:381:debian-bookworm-gcc-arm32-randconfig:
>> gitlab-ci/build.yaml:429:alpine-3.18-gcc-arm64-randconfig:
>> gitlab-ci/build.yaml:495:archlinux-current-gcc-riscv64-randconfig:
>> gitlab-ci/build.yaml:640:debian-bookworm-gcc-randconfig:
>>
>> as PPC64 doesn't want randconfig right now, and buster-gcc-ibt is a special
>> job with a custom compiler.
>>
>> Signed-off-by: Andrew Cooper <[email protected]>
> Reviewed-by: Anthony PERARD <[email protected]>
Thanks.
>
> Thanks,
>
>> If we want to run multiple identical randconfig jobs, that's spelt
>>
>> parallel: 5
>>
>> in the configuration, and here is an example of what such a run looks like:
>> https://gitlab.com/xen-project/people/andyhhp/xen/-/pipelines/1368824041
>>
>> Notice the randconfig jobs have a 5 in place of a retry button, and show a
>> submenu when clicked on.
> We already have "parallel: 2" on the whole pipeline, give or take, but
> those are quick jobs so it might be worth it to run them a few more time
> on a pipeline.
I'm afraid I don't follow.
The runners themselves are set up to run concurrent jobs. I could well
believe that's spelt parallel: in the runner config files.
Here, its really jobs:parallel which is the way of saying "I want 5
copies of this job to run in the pipeline".
Obviously, 5 is arbitrary. I was thinking of having a scheduled (once
per day, at 3AM or whenever) running randconfig only with a parallel:20
or so, so we can make good use of otherwise-idle time.
~Andrew
