linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3] xfstests/btrfs: add qgroup rescan stress test
Date: Wed, 18 Jun 2014 08:24:12 -0700	[thread overview]
Message-ID: <53A1AF1C.6070204@fb.com> (raw)
In-Reply-To: <53A14F86.9000506@cn.fujitsu.com>



On 06/18/2014 01:36 AM, Wang Shilong wrote:
> Hello Josef,
>
> The lastest Qgroup code still break this test sometimes.
>
> Ps: this test seems not merging into xfstests.
>

Yeah Chris said something about this yesterday, I'll try and get a vm up 
and running on my laptop soon and take a look at this.  Just resend this 
to the fstests list and make sure to include my reviewed-by, this test 
is super important.  Thanks,

Josef

  reply	other threads:[~2014-06-18 15:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10  3:44 [PATCH v2 1/3] xfstests/btrfs: add qgroup rescan stress test Wang Shilong
2014-03-10  3:44 ` [PATCH v2 2/3] xfstests/btrfs: add basic functional test for btrfs quota groups Wang Shilong
2014-03-10 19:46   ` Josef Bacik
2014-03-10  3:44 ` [PATCH v2 3/3] xfstests/btrfs: add stress test for btrfs quota operations Wang Shilong
2014-03-10 19:48   ` Josef Bacik
2014-03-13  3:12     ` Dave Chinner
2014-03-13 14:02       ` Josef Bacik
2014-03-10 19:43 ` [PATCH v2 1/3] xfstests/btrfs: add qgroup rescan stress test Josef Bacik
2014-03-11  1:19   ` Wang Shilong
2014-05-07 20:58 ` Josef Bacik
2014-05-08  3:38   ` Wang Shilong
2014-05-08 18:33     ` Josef Bacik
2014-05-09  1:17       ` Wang Shilong
2014-05-09  2:13         ` Josef Bacik
2014-05-09  2:43           ` Wang Shilong
2014-05-09 17:24             ` Josef Bacik
2014-05-09  6:02 ` [PATCH v3] " Wang Shilong
2014-05-09 17:32   ` Josef Bacik
2014-06-18  8:36   ` Wang Shilong
2014-06-18 15:24     ` Josef Bacik [this message]
2014-06-19  0:51     ` 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=53A1AF1C.6070204@fb.com \
    --to=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangsl.fnst@cn.fujitsu.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).