public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Iliopoulos <ailiop@suse.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] generic/682: update and fix-up golden output
Date: Tue, 6 Feb 2024 18:31:42 +0100	[thread overview]
Message-ID: <ZcJs_jsbiTpx6HyO@technoir> (raw)
In-Reply-To: <20240202115605.he7ciqxubrlglnzh@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Fri, Feb 02, 2024 at 07:56:05PM +0800, Zorro Lang wrote:
> On Thu, Feb 01, 2024 at 05:17:32PM +0100, Anthony Iliopoulos wrote:
> > coreutils v9.4 introduced a change in the error output of mv under
> > certain errno values via commit 3cb862ce5f10 ("mv: better diagnostic for
> > 'mv dir x' failure"), which broke the golden output.
> > 
> > Update golden output to match the change, and further add an output
> > filter to avoid having the test fail on environments that ran with an
> > older coreutils release, taken from commit d9323ad7a05e ("generic/245:
> > Filter mv error message").
> > 
> > Signed-off-by: Anthony Iliopoulos <ailiop@suse.com>
> > ---
> >  tests/generic/682     | 8 +++++++-
> >  tests/generic/682.out | 2 +-
> >  2 files changed, 8 insertions(+), 2 deletions(-)
> > 
> > diff --git a/tests/generic/682 b/tests/generic/682
> > index a51d18338742..417598804bde 100755
> > --- a/tests/generic/682
> > +++ b/tests/generic/682
> > @@ -54,6 +54,12 @@ repquota -upn $SCRATCH_MNT >> $seqres.full
> >  echo $(ls $scratchdir | wc -l) files in $scratchdir  >> $seqres.full
> >  ls -sld $scratchdir  >> $seqres.full
> >  
> > +_filter_mv_output()
> > +{
> > +	sed -e "s,cannot move .* to \(.*\):\(.*\),cannot overwrite \1:\2,g" \
> 
> Hi Anthony,
> 
> Thanks for this fix, I remember there's a mv filter in generic/245, we
> just merged a patch same with above line:
>   d9323ad7a05e ("generic/245: Filter mv error message")
> 
> I think you can merge the _filter_directory_not_empty() of g/245 with
> this patch into one _filter_mv_output() function, and call it in g/245
> and g/682 (check if there're more cases need mv output).

Make sense, I'll send out a v2 shortly with the filters consolidated.

AFAICT only g/245 and g/682 are affected by the particular coreutils mv
error output change, due to their golden output.

The only other tests are g/{369,419}:

$ git grep 'cannot move' tests/
tests/generic/369.out:mv: cannot move 'h' to 'd7/h': Permission denied
tests/generic/369.out:mv: cannot move 'h' to 's7/h': Permission denied
tests/generic/419.out:mv: cannot move 'SCRATCH_MNT/edir/NOKEY_NAME' to
'SCRATCH_MNT/edir/NOKEY_NAME': Required key not available

but those aren't affected as coreutils commit 3cb862ce5f10 only changed
the error output for specific err codes (EDQUOT, EEXIST, EISDIR, EMLINK,
ENOSPC, ENOTEMPTY, ETXTBSY), while g/369 is expecting EPERM and g/419 is
ENOKEY.

Regards,
Anthony

      reply	other threads:[~2024-02-06 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 16:17 [PATCH 0/2] generic/681 and generic/682 fixes Anthony Iliopoulos
2024-02-01 16:17 ` [PATCH 1/2] generic/68[12]: use the dir blocksize for xfs filesystems Anthony Iliopoulos
2024-02-02 10:56   ` Andrey Albershteyn
2024-02-01 16:17 ` [PATCH 2/2] generic/682: update and fix-up golden output Anthony Iliopoulos
2024-02-02 11:00   ` Andrey Albershteyn
2024-02-02 11:56   ` Zorro Lang
2024-02-06 17:31     ` Anthony Iliopoulos [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=ZcJs_jsbiTpx6HyO@technoir \
    --to=ailiop@suse.com \
    --cc=fstests@vger.kernel.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