From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: state of the testsuite
Date: Tue, 5 Jun 2007 01:02:22 +1000 [thread overview]
Message-ID: <20070604150222.GL86004887@sgi.com> (raw)
In-Reply-To: <20070604144441.GA9672@lst.de>
On Mon, Jun 04, 2007 at 04:44:41PM +0200, Christoph Hellwig wrote:
> When running the testsuite on Debian -testing I constanyly get the
> 12 failing testcases (016 041 049 064 071 082 084 104 111 136 140 166).
> Is this expected or are other people seeing better results?
What kernel+platform and what version of the tests?
Prior to 2.6.22-rc2, 016 and 144 are the only ones i saw failing
regularly. 166 will fail until we get ->page_mkwrite
sorted out (but passes in my tree).
With 2.6.22-rc2, all the loopback based tests are failing
because someone broke the loopback device so lots of tests
fail because of that. The other tests I haven't seen fail
for some time...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-06-04 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 14:44 state of the testsuite Christoph Hellwig
2007-06-04 15:02 ` David Chinner [this message]
2007-06-04 15:12 ` David Chinner
2007-06-04 15:13 ` Christoph Hellwig
2007-06-04 17:21 ` Christoph Hellwig
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=20070604150222.GL86004887@sgi.com \
--to=dgc@sgi.com \
--cc=hch@lst.de \
--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