qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>
Cc: Hanna Czenczek <hreitz@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
	Kevin Wolf <kwolf@redhat.com>
Subject: Re: io-qcow2 failures on zfs
Date: Fri, 26 May 2023 10:02:02 +0200	[thread overview]
Message-ID: <333138b6-401b-d863-c2cf-90e36d16cc97@redhat.com> (raw)
In-Reply-To: <d1ab807e-3a9a-91b9-ad52-2d46c06ff54b@linaro.org>

On 25/05/2023 20.29, Richard Henderson wrote:
> Ping.
> 
> On 5/19/23 15:44, Richard Henderson wrote:
>> I'm doing some testing on one of the Linaro build machines and I reliably see
>>
>> Summary of Failures:
>>
>> 712/790 qemu:block / 
>> io-qcow2-150                                                 ERROR         
>> 5.24s   exit status 1
>> 777/790 qemu:block / 
>> io-qcow2-copy-before-write                                   ERROR        
>> 16.31s   exit status 1
>> 779/790 qemu:block / 
>> io-qcow2-244                                                 ERROR        
>> 37.10s   exit status 1
>>
>> This is x86_64 ubuntu 22.04, same as my laptop, so the only thing I can 
>> think is the filesystem type:
>>
>> hackpool-0/home/richard.henderson /home/richard.henderson zfs 
>> rw,nosuid,nodev,noatime,xattr,noacl 0 0
>>
>> Any thoughts?

What output do you get when running the tests directly? i.e.:

cd tests/qemu-iotests/
./check -qcow2 150
./check -qcow2 copy-before-write
./check -qcow2 244

  Thomas



  reply	other threads:[~2023-05-26  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 22:44 io-qcow2 failures on zfs Richard Henderson
2023-05-25 18:29 ` Richard Henderson
2023-05-26  8:02   ` Thomas Huth [this message]
2023-05-26 15:47     ` Richard Henderson

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=333138b6-401b-d863-c2cf-90e36d16cc97@redhat.com \
    --to=thuth@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=vsementsov@yandex-team.ru \
    /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).