fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eryu Guan <guan@eryu.me>
To: Christoph Hellwig <hch@infradead.org>
Cc: fstests@vger.kernel.org, zlang@redhat.com
Subject: Re: generic/095 and generic/300 failures
Date: Sun, 25 Apr 2021 13:05:35 +0800	[thread overview]
Message-ID: <YIT4n/154e/vOm9H@desktop> (raw)
In-Reply-To: <YH5siAMU+6p7iD01@infradead.org>

On Tue, Apr 20, 2021 at 07:54:16AM +0200, Christoph Hellwig wrote:
> Hi all,
> 
> generic/095 and generic/300 have been failing for me with every config
> on every file system for a while with the following messages:
> 
> --- tests/generic/095.out	2016-03-29 13:59:30.405053956 +0000
> +++ results/generic/095.out.bad	2021-04-20 05:44:54.432081845 +0000
> @@ -1,2 +1,7 @@
>  QA output created by 095
> +job9: No I/O performed by mmap, perhaps try --debug=io option for details?
> +job9: No I/O performed by mmap, perhaps try --debug=io option for details?
> +job9: No I/O performed by mmap, perhaps try --debug=io option for details?
> +job9: No I/O performed by mmap, perhaps try --debug=io option for details?
> +job9: No I/O performed by mmap, perhaps try --debug=io option for details?
>  Silence is golden           
> 
> --- tests/generic/300.out	2016-03-29 13:59:30.431720622 +0000
> +++ results/generic/300.out.bad	2021-04-20 05:45:06.324708699 +0000
> @@ -2,3 +2,4 @@
>  
>  Run fio with random aio-dio pattern
>    
> +falloc_raicer: No I/O performed by falloc, perhaps try --debug=io option for details?
> 
> 
> ----- End forwarded message -----

Yeah, I've noticed these failures as well, and it seems that it's caused
by fio behavior change, as Zorro said he never hit such failures[1].

I'm using fio-3.7

# fio --version
fio-3.7-66-gedfc

Thanks,
Eryu

[1] https://www.spinics.net/lists/fstests/msg15871.html

  reply	other threads:[~2021-04-25  5:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  5:54 generic/095 and generic/300 failures Christoph Hellwig
2021-04-25  5:05 ` Eryu Guan [this message]
2021-04-25  6:48   ` Zorro Lang

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=YIT4n/154e/vOm9H@desktop \
    --to=guan@eryu.me \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=zlang@redhat.com \
    /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).