From: Mark Tinguely <tinguely@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: v2 xfs directory unbalance assert test
Date: Tue, 17 Sep 2013 17:14:19 -0500 [thread overview]
Message-ID: <5238D43B.5010808@sgi.com> (raw)
In-Reply-To: <5238CB32.2090404@sandeen.net>
On 09/17/13 16:35, Eric Sandeen wrote:
> On 9/17/13 4:34 PM, Dave Chinner wrote:
>> On Tue, Sep 17, 2013 at 02:25:23PM -0500, Mark Tinguely wrote:
>>> This tests triggers an assert in the XFS directory unbalance code.
>>> This test originally written by Brian Foster and suggestions
>>> from Micheal Semon.
>>>
>>> Signed-off-by: Mark Tinguely<tinguely@sgi.com>
>>> ---
>>> v1->v2:
>>> remove clean up.
>>> remove $seqres.full before test.
>>> remove scratch mount.
>>> 11g -> calculate 11g bytes.
>>> check for failing mkfs and mount.
>>> add a safer removal of the scratch files.
>>>
>>> put into auto group and "long" group so people can opt out:
>>> this test almost an hour on my test box.
>>
>> 45m is too long for the auto group. The entire auto group runs in
>> 50-55 minutes on my test VMs, so doubling that for one test is not
>> really a good idea.
>
> Ok, sorry, my fault. Fix on commit?
>
> -Eric
We can't remove much more and still hit the assert, so I am happy to
remove it from the auto group.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-17 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 19:25 [PATCH] xfstests: v2 xfs directory unbalance assert test Mark Tinguely
2013-09-17 19:37 ` Eric Sandeen
2013-09-17 20:03 ` Mark Tinguely
2013-09-17 21:34 ` Dave Chinner
2013-09-17 21:35 ` Eric Sandeen
2013-09-17 22:14 ` Mark Tinguely [this message]
2013-09-18 16:36 ` Michael L. Semon
2013-09-18 17:43 ` Mark Tinguely
2013-09-23 23:30 ` Dave Chinner
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=5238D43B.5010808@sgi.com \
--to=tinguely@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.