From: "Barry Naujok" <bnaujok@melbourne.sgi.com>
To: nscott@aconex.com, xfs@oss.sgi.com
Subject: RE: QA regression test issues
Date: Fri, 8 Dec 2006 11:16:55 +1100 [thread overview]
Message-ID: <200612080010.LAA29025@larry.melbourne.sgi.com> (raw)
In-Reply-To: <1165536274.30459.51.camel@edge>
Yes, xfs_repair has more progress information in recent versions. The
XFS QA tests are being updated with new xfs_repair filterings to filter
out that progress info as it's not required for QA.
I'll be doing further xfs_repair output cleanup at a later stage.
> -----Original Message-----
> From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com]
> On Behalf Of Nathan Scott
> Sent: Friday, 8 December 2006 11:05 AM
> To: xfs@oss.sgi.com
> Subject: QA regression test issues
>
> Hi,
>
> Is it just me or are many of the QA tests broken with current versions
> of xfs_repair? In the "repair" check group, 3 out of 5 tests are not
> passing atm (with/without my last coupla patches).
>
> Can the person who broke 'em, fix 'em please? :) Thanks!
>
> cheers.
>
> --
> Nathan
>
>
parent reply other threads:[~2006-12-08 0:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1165536274.30459.51.camel@edge>]
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=200612080010.LAA29025@larry.melbourne.sgi.com \
--to=bnaujok@melbourne.sgi.com \
--cc=nscott@aconex.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox