qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: iotests failing on gitlab CI check-system-fedora job


From: Paolo Bonzini
Subject: Re: iotests failing on gitlab CI check-system-fedora job
Date: Thu, 18 Mar 2021 11:37:45 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]