| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfstest failures |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Thu, 07 Nov 2013 07:24:28 -0600 |
| Cc: | Ben Myers <bpm@xxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20131107081710.GC25157@xxxxxxxxxxxxx> |
| References: | <20131106105451.GA31283@xxxxxxxxxxxxx> <20131106161825.GU1935@xxxxxxx> <527A887F.2030807@xxxxxxxxxxx> <20131107081710.GC25157@xxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
On 11/7/13, 2:17 AM, Christoph Hellwig wrote: > On Wed, Nov 06, 2013 at 12:20:47PM -0600, Eric Sandeen wrote: >> that's right, it's a known bug w/ a testcase but no fix yet. >> >> I looked a bit, but ugh, xfsdump. > > Maybe it's time you come up with an xfail mechanism at least? What's the proposal there, a "fail" group for things known to still fail everywhere? so i.e. ./check -x fail ? I can easily send a patch for that if that's what folks want. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH v2] xfs: fix unlock in xfs_bmap_add_attrfork, Mark Tinguely |
|---|---|
| Next by Date: | Re: xfstest failures, Mark Tinguely |
| Previous by Thread: | Re: xfstest failures, Christoph Hellwig |
| Next by Thread: | Re: xfstest failures, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |