All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <esandeen@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: Baihua Lu <lubaihua0331@gmail.com>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: xfs/191 failures?
Date: Wed, 15 Jan 2020 12:07:47 -0600	[thread overview]
Message-ID: <ae0bc15b-efcb-89e3-4e6e-7c60aab1c3a5@redhat.com> (raw)
In-Reply-To: <20200115162126.GY8247@magnolia>



On 1/15/20 10:21 AM, Darrick J. Wong wrote:
> On Wed, Jan 15, 2020 at 07:08:02AM -0800, Christoph Hellwig wrote:
>> Hi Jan and Baihua,
>>
>> the xfs/191 test case has been failing for me basically since it
>> was added.  Does it succeed for anyone with an upstream kernel
>> and xfsprogs?
> 
> It never succeeds here.

<Jan has left Red Hat>

yeah I think this has always been a mess, not sure why it took so long to
highlight it.  Seems like a combination of WTF? and general rot.

> --D
> 
>> Here is my diff between the golden and the actual
>> output:
> 
>> --- /root/xfstests/tests/xfs/191-input-validation.out	2016-09-21 20:34:14.961574921 +0000
>> +++ /root/xfstests/results//xfs/191-input-validation.out.bad	2020-01-15 15:05:25.580935340 +0000
>> @@ -1,2 +1,13 @@
>>  QA output created by 191-input-validation
>>  silence is golden

supposedly these should fail, but they pass:

>> +pass -n size=2b /dev/vdc
>> +pass -d agsize=8192b /dev/vdc
>> +pass -d agsize=65536s /dev/vdc

I don't know why it wouldn't be valid to use block & sector units for these
values.  But this whole mkfs reworking discussion was so long ago :(

>> +pass -d su=0,sw=64 /dev/vdc

not sure why this passes

>> +pass -d su=4096s,sw=64 /dev/vdc
>> +pass -d su=4096b,sw=64 /dev/vdc

s & b suffixes seem to be ignored here, which seems like a bug.

>> +pass -l su=10b /dev/vdc

again this seems to DTRT.


according to the test, these should pass, but they fail:

>> +fail -n log=15 /dev/vdc

uh, "-n log=" isn't even a mkfs option so of course it fails

>> +fail -r rtdev=/mnt/test/191-input-validation.img /dev/vdc

this fails because reflink is default now

>> +fail -r size=65536,rtdev=/mnt/test/191-input-validation.img /dev/vdc

ditto

>> +fail -i log=10 /dev/vdc

-i log is not a valid option either so of course it fails.

My first thought was to nuke it all, but I think the test could be salvaged
by anyone motivated to do so.

-Eric


      reply	other threads:[~2020-01-15 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 15:08 xfs/191 failures? Christoph Hellwig
2020-01-15 16:21 ` Darrick J. Wong
2020-01-15 18:07   ` Eric Sandeen [this message]

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=ae0bc15b-efcb-89e3-4e6e-7c60aab1c3a5@redhat.com \
    --to=esandeen@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lubaihua0331@gmail.com \
    --cc=sandeen@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 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.