From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Laurent Vivier <lvivier@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Qemu-block <qemu-block@nongnu.org>
Subject: Re: iotests failing on gitlab CI check-system-fedora job
Date: Thu, 18 Mar 2021 00:26:19 +0100 [thread overview]
Message-ID: <6f3cd467-5013-a372-28f7-f1ca0b1f1d03@redhat.com> (raw)
In-Reply-To: <CAFEAcA_cZYF9u8RfW5mUY7TgOLsRYh1sN7oioztfSV8_990peg@mail.gmail.com>
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
next prev parent reply other threads:[~2021-03-17 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 22:23 iotests failing on gitlab CI check-system-fedora job Peter Maydell
2021-03-17 23:26 ` Paolo Bonzini [this message]
2021-03-18 10:07 ` Peter Maydell
2021-03-18 10:37 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6f3cd467-5013-a372-28f7-f1ca0b1f1d03@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).