Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Steve French <smfrench@gmail.com>
Cc: dhowells@redhat.com, CIFS <linux-cifs@vger.kernel.org>
Subject: Re: generic/075 and generic/112 regression
Date: Sat, 24 Aug 2024 13:15:50 +0100	[thread overview]
Message-ID: <564363.1724501750@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAH2r5muJabg=dB9EkuZD26+2mnQGRYRbpbQ96UxTk2UF4ZNQ6g@mail.gmail.com>

Steve French <smfrench@gmail.com> wrote:

> We are still getting a failure with the netfs/cifs changes in
> generic/075 and generic/112
> 
> http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/9/builds/119

What's in the output files for 075?

I'm seeing:

+    fsx (-d -N 1000 -S 0) failed, 0 - compare /root/xfstests-dev/results//smb3/generic/075.0.{good,bad,fsxlog}
+mv: '/root/xfstests-dev/results//smb3/generic/075.0.fsxlog' and '/root/xfstests-dev/results//smb3/generic/075.0.fsxlog' are the same file

David


      reply	other threads:[~2024-08-24 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-24  1:05 generic/075 and generic/112 regression Steve French
2024-08-24 12:15 ` David Howells [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=564363.1724501750@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.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