* iotests failing on gitlab CI check-system-fedora job
@ 2021-03-17 22:23 Peter Maydell
2021-03-17 23:26 ` Paolo Bonzini
0 siblings, 1 reply; 4+ messages in thread
From: Peter Maydell @ 2021-03-17 22:23 UTC (permalink / raw)
To: QEMU Developers; +Cc: Qemu-block
The check-system-fedora job in the gitlab CI seems to have
started reliably failing on iotests 040 041 127 256 267:
https://gitlab.com/qemu-project/qemu/-/jobs/1106977551
Could somebody have a look at what's happening, please?
(This is probably a regression that's got into master because
I stopped using "did gitlab CI pass" as a gate because gitlab
was running massively too slowly to be usable for that.)
thanks
-- PMM
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iotests failing on gitlab CI check-system-fedora job
2021-03-17 22:23 iotests failing on gitlab CI check-system-fedora job Peter Maydell
@ 2021-03-17 23:26 ` Paolo Bonzini
2021-03-18 10:07 ` Peter Maydell
0 siblings, 1 reply; 4+ messages in thread
From: Paolo Bonzini @ 2021-03-17 23:26 UTC (permalink / raw)
To: Peter Maydell, QEMU Developers; +Cc: Laurent Vivier, Kevin Wolf, Qemu-block
On 17/03/21 23:23, Peter Maydell wrote:
> The check-system-fedora job in the gitlab CI seems to have
> started reliably failing on iotests 040 041 127 256 267:
> https://gitlab.com/qemu-project/qemu/-/jobs/1106977551
>
> Could somebody have a look at what's happening, please?
> (This is probably a regression that's got into master because
> I stopped using "did gitlab CI pass" as a gate because gitlab
> was running massively too slowly to be usable for that.)
It's caused by adding virtio devices to the m68k target. Probably it
can be fixed by moving i386-softmmu to Fedora and m68k-softmmu to Debian.
But really, most of the tests we run are not ever going to fail in
isolation. Do we really gain anything by building all or almost all
targets for each cross (as opposed to just one 32-bit and one 64-bit
target), or by running check-block many times on similar or identical
configurations?
Paolo
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iotests failing on gitlab CI check-system-fedora job
2021-03-17 23:26 ` Paolo Bonzini
@ 2021-03-18 10:07 ` Peter Maydell
2021-03-18 10:37 ` Paolo Bonzini
0 siblings, 1 reply; 4+ messages in thread
From: Peter Maydell @ 2021-03-18 10:07 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Laurent Vivier, Kevin Wolf, QEMU Developers, Qemu-block
On Wed, 17 Mar 2021 at 23:26, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 17/03/21 23:23, Peter Maydell wrote:
> > The check-system-fedora job in the gitlab CI seems to have
> > started reliably failing on iotests 040 041 127 256 267:
> > https://gitlab.com/qemu-project/qemu/-/jobs/1106977551
> >
> > Could somebody have a look at what's happening, please?
> > (This is probably a regression that's got into master because
> > I stopped using "did gitlab CI pass" as a gate because gitlab
> > was running massively too slowly to be usable for that.)
>
> It's caused by adding virtio devices to the m68k target. Probably it
> can be fixed by moving i386-softmmu to Fedora and m68k-softmmu to Debian.
Why are the iotests not specifying what machine type they run
on if they care about the machine type ?
thanks
-- PMM
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iotests failing on gitlab CI check-system-fedora job
2021-03-18 10:07 ` Peter Maydell
@ 2021-03-18 10:37 ` Paolo Bonzini
0 siblings, 0 replies; 4+ messages in thread
From: Paolo Bonzini @ 2021-03-18 10:37 UTC (permalink / raw)
To: Peter Maydell; +Cc: Laurent Vivier, Kevin Wolf, QEMU Developers, Qemu-block
On 18/03/21 11:07, Peter Maydell wrote:
> On Wed, 17 Mar 2021 at 23:26, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> On 17/03/21 23:23, Peter Maydell wrote:
>>> The check-system-fedora job in the gitlab CI seems to have
>>> started reliably failing on iotests 040 041 127 256 267:
>>> https://gitlab.com/qemu-project/qemu/-/jobs/1106977551
>>>
>>> Could somebody have a look at what's happening, please?
>>> (This is probably a regression that's got into master because
>>> I stopped using "did gitlab CI pass" as a gate because gitlab
>>> was running massively too slowly to be usable for that.)
>>
>> It's caused by adding virtio devices to the m68k target. Probably it
>> can be fixed by moving i386-softmmu to Fedora and m68k-softmmu to Debian.
>
> Why are the iotests not specifying what machine type they run
> on if they care about the machine type ?
Because the intersection of people building only "uncommon" targets and
people running "check-block" is usually empty. Adjusting
tests/qemu-iotests/testenv.py should be quite easy though.
Paolo
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-03-18 10:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-17 22:23 iotests failing on gitlab CI check-system-fedora job Peter Maydell
2021-03-17 23:26 ` Paolo Bonzini
2021-03-18 10:07 ` Peter Maydell
2021-03-18 10:37 ` Paolo Bonzini
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.