From: Eric Sandeen <sandeen@sandeen.net>
To: Steve French <smfrench@gmail.com>,
fstests@vger.kernel.org,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: xfstest generic/299
Date: Thu, 22 Jan 2015 23:35:36 -0600 [thread overview]
Message-ID: <54C1DDA8.5040103@sandeen.net> (raw)
In-Reply-To: <CAH2r5mvSUc0-Z1Kn3NfowUzH1Jw4x_8UF46+uXKBPshuFkb1dw@mail.gmail.com>
On 1/22/15 11:23 PM, Steve French wrote:
> Noticed test generic/299 failing over NFS (v4.1 dialect) with the error
>
> "[not run] /usr/bin/fio too old"
>
> fio-2.1.11 version (which is what is installed on current Ubuntu) is
> presumably not too old
Well, 2.1.11 was released 16-Jul-2014
fio is up to 2.2.5 now, so it sure could be.
The test sets up a config file, and tries to run fio against it;
if it fails, it's deemed "too old"
And _require_fio dumps to $seqres.full,
$FIO_PROG --warnings-fatal --showcmd $job >> $seqres.full 2>&1
[ $? -eq 0 ] || _notrun "$FIO_PROG too old, see $seqres.full"
so what does 299.full look like?
-Eric
next prev parent reply other threads:[~2015-01-23 5:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 5:23 xfstest generic/299 Steve French
2015-01-23 5:35 ` Eric Sandeen [this message]
2015-01-23 20:09 ` Steve French
2015-01-23 20:17 ` Steve French
2015-01-23 20:28 ` Eric Sandeen
2015-01-23 20:25 ` Eric Sandeen
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=54C1DDA8.5040103@sandeen.net \
--to=sandeen@sandeen.net \
--cc=fstests@vger.kernel.org \
--cc=linux-nfs@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