Re: [PULL 00/17] CI job updates, header cleanups and other misc patches

[Thomas Huth]

On 25/04/2024 17.04, Richard Henderson wrote:
> On 4/24/24 22:11, Thomas Huth wrote:
> > On 24/04/2024 18.21, Richard Henderson wrote:
> > > On 4/24/24 00:57, Thomas Huth wrote:
> > > > The following changes since commit 
> > > > 13b1e9667737132440f4d500c31cb69320c6b15a:
> > > >
> > > >    Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into 
> > > > staging (2024-04-23 17:35:57 -0700)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > >    https://gitlab.com/thuth/qemu.git tags/pull-request-2024-04-24
> > > >
> > > > for you to fetch changes up to 8f29bab03ea22694a127ee33edeb4ce99eeb124e:
> > > >
> > > >    target/s390x: Remove KVM stubs in cpu_models.h (2024-04-24 09:45:02 
> > > > +0200)
> > > >
> > > > ----------------------------------------------------------------
> > > > * Update OpenBSD CI image to 7.5
> > > > * Update/remove Ubuntu 20.04 CI jobs
> > > > * Update CentOS 8 CI jobs to CentOS 9
> > > > * Some clean-ups and improvements to travis.yml
> > > > * Minor test fixes
> > > > * s390x header clean-ups
> > > > * Doc updates
> > >
> > > This introduces a failure in the migration-compat-x86_64 job:
> > >
> > > https://gitlab.com/qemu-project/qemu/-/jobs/6707154868
> >
> > It wasn't failing for me:
> >
> >   https://gitlab.com/thuth/qemu/-/jobs/6702058896
> >
> > And according to the diffstat of my pull request, it's only touching test 
> > files, docs, and s390x stuff, so I somehow fail to see how it could 
> > influence x86 migration at a first glance. It also looks like the job is 
> > running on opensuse, and not on CentOS or Ubuntu, so it should likely not 
> > be influenced by the changes in this PR.
> >
> > Could you please hit the re-run button of that job? If it then passes, 
> > we're likely rather facing an intermitted failure that might have been 
> > introduced earlier already...
>
> It did pass when re-run.

Ok, thanks! So it's likely and intermitted problem indeed...

I've now submitted a v2 of the pull request where I just dropped the other 
problematic patch that tried to update the custom CentOS runner ... I hope 
that PR should be fine now.

 Thomas