Re: xen | Failed pipeline for staging | 9dd3caf1

[Julien Grall <julien@xxxxxxx>]

Hi,

On 04/07/2023 16:50, Andrew Cooper wrote:
> On 04/07/2023 4:39 pm, Jan Beulich wrote:
> > On 30.06.2023 16:50, GitLab wrote:
> > > Pipeline #917215286 has failed!
> > >
> > > Project: xen ( https://gitlab.com/xen-project/xen )
> > > Branch: staging ( https://gitlab.com/xen-project/xen/-/commits/staging )
> > >
> > > Commit: 9dd3caf1 ( 
> > > https://gitlab.com/xen-project/xen/-/commit/9dd3caf12f52b859947c260b1cb3a48b491d53b6
> > >  )
> > > Commit Message: {x86,arm}/mm.c: Make populate_pt_range __init
> > >
> > > ...
> > > Commit Author: George Dunlap
> > > Committed by: George Dunlap
> > >
> > >
> > > Pipeline #917215286 ( https://gitlab.com/xen-project/xen/-/pipelines/917215286 
> > > ) triggered by Ganis ( https://gitlab.com/ganis )
> > > had 3 failed jobs.
> > >
> > > Job #4573553348 ( https://gitlab.com/xen-project/xen/-/jobs/4573553348/raw )
> > >
> > > Stage: build
> > > Name: opensuse-tumbleweed-gcc-debug
> > > Job #4573553345 ( https://gitlab.com/xen-project/xen/-/jobs/4573553345/raw )
> > >
> > > Stage: build
> > > Name: opensuse-tumbleweed-gcc
> > While iirc the above continue to be expected, ...
> >
> > > Job #4573553188 ( https://gitlab.com/xen-project/xen/-/jobs/4573553188/raw )
> > >
> > > Stage: build
> > > Name: debian-unstable-gcc-debug-arm64-randconfig
> > ... this one has
> >
> > ld    -EL --no-warn-rwx-segments -T arch/arm/xen.lds -N prelink.o \
> >      ./common/symbols-dummy.o -o ./.xen-syms.0
> > ld: Xen is too big
> >
> > in its build log. Whatever the .config, I'm inclined to say this should
> > not happen.
This was a latent bug because building Xen with GCOV will result to a 
binary bigger than 2MB (the max size we currently support)
The ASSERT() makes it more obvious. I am not sure why we never gated 
GCOV with !ARM as I don't see how this could have booted. Anyway...
> That is
> https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=02a11313cdc60d266d8613899fcc9d3870ef5164
> and is intermittent when randconfig chooses COVERAGE
>
> "[v2 0/4] xen/arm: Enable USBAN support" on list should fix it.
... I have now committed the series. So randconfig should not fail anymore.

Cheers,

--
Julien Grall