linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>, Xiaoli Feng <xifeng@redhat.com>
Subject: Re: xfstests passing again to current for-next
Date: Tue, 5 Mar 2019 19:16:55 -0600	[thread overview]
Message-ID: <CAH2r5mskbS9WVKYYr++LP6FpkH1a6JXVZivuyX3T+ZqmG=a9pg@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5msbsfxHULn--6Y4SXxQRezrOhU65JMXRKA0rV0bhCMNcw@mail.gmail.com>

And DFS set of tests passed as well

On Tue, Mar 5, 2019 at 6:26 PM Steve French <smfrench@gmail.com> wrote:
>
> I also reran (directly on the buildbot)  the subtests which seemed a
> bit slower in that run earlier today - and most looked fine with
> possible exception of test 112 which seems about 20% slower than I
> would have expected.
>
> generic/001     163s
> generic/024     12s
> generic/100     278s
> generic/112     319s
> generic/117     141s
> generic/124     49s
> generic/129     530s
> generic/133     454s
> generic/198     3s
> generic/247     95s
> generic/249     2s
> generic/285     8s
> generic/286     30s
> generic/310     311s
> generic/406     4s
> generic/432     3s
> generic/524     16s
> Ran: generic/001 generic/024 generic/100 generic/112 generic/117
> generic/124 generic/129 generic/133 generic/198 generic/247
> generic/249 generic/285 generic/286 generic/310 generic/406
> generic/432 generic/524
> Passed all 17 tests
>
> On Tue, Mar 5, 2019 at 5:45 PM Steve French <smfrench@gmail.com> wrote:
> >
> > Moved the xfstest git branch back to December 6th (just before the
> > testcase problem patch Xiaoli pointed out) - and cherrypicked tests
> > 524 and 528.  Looks like current for-next worked fine
> > (http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/4/builds/111).
> > Will  kick off the cifs-testing bucket later today.
> >
> > --
> > Thanks,
> >
> > Steve
>
>
>
> --
> Thanks,
>
> Steve



-- 
Thanks,

Steve

      reply	other threads:[~2019-03-06  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05 23:45 xfstests passing again to current for-next Steve French
2019-03-06  0:26 ` Steve French
2019-03-06  1:16   ` Steve French [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='CAH2r5mskbS9WVKYYr++LP6FpkH1a6JXVZivuyX3T+ZqmG=a9pg@mail.gmail.com' \
    --to=smfrench@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=xifeng@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).