Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Aurélien Aptel" <aaptel@suse.com>
To: Murphy Zhou <jencce.kernel@gmail.com>, linux-cifs@vger.kernel.org
Subject: Re: Are the xfstests exclusion files on wiki.samba.org up to date?
Date: Mon, 09 Sep 2019 12:50:09 +0200	[thread overview]
Message-ID: <87mufdiw0u.fsf@suse.com> (raw)
In-Reply-To: <20190909104127.nsdxptzxcf5a6b72@XZHOUW.usersys.redhat.com>

"Murphy Zhou" <jencce.kernel@gmail.com> writes:
> As $subject. Is this wiki being maintained ?
>
> Looks like the last update was in January 2019.
>
> https://wiki.samba.org/index.php/Xfstesting-cifs#Exclusion_files

We have a buildbot running xfstests relatively often here

http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/

Each group has slightly different tests run, you can see which one gets
run by clicking on a build:

http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/249

Overall xfstests+cifs is very finicky and frustrating to get working
reliably. Not to mention long. So good luck :)

Cheers,
-- 
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)

  reply	other threads:[~2019-09-09 10:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09 10:41 Are the xfstests exclusion files on wiki.samba.org up to date? Murphy Zhou
2019-09-09 10:50 ` Aurélien Aptel [this message]
2019-09-09 23:23   ` Steve French
2019-09-10 10:39     ` ronnie sahlberg
2019-09-10 11:41       ` Aurélien Aptel
2019-09-12  8:50         ` Murphy Zhou
2019-09-12  8:49     ` Murphy Zhou
2019-09-12  9:06       ` ronnie sahlberg
2019-09-14  0:02         ` Murphy Zhou
     [not found]           ` <CAH2r5mv5RqAfAMb2oWa+10bqUa+6kUMO3HKPG1s2z0PRqOeKEg@mail.gmail.com>
2019-09-14  0:44             ` Murphy Zhou
2019-09-12  8:45   ` Murphy Zhou

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=87mufdiw0u.fsf@suse.com \
    --to=aaptel@suse.com \
    --cc=jencce.kernel@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    /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