From: Alex Elder <aelder@sgi.com>
To: sekharan@us.ibm.com
Cc: XFS Mailing List <xfs@oss.sgi.com>
Subject: Re: xfstests test case 180 fails often
Date: Thu, 16 Jun 2011 16:29:22 -0500 [thread overview]
Message-ID: <1308259762.2717.31.camel@doink> (raw)
In-Reply-To: <1308077464.7661.473.camel@chandra-lucid.beaverton.ibm.com>
On Tue, 2011-06-14 at 11:51 -0700, Chandra Seetharaman wrote:
> Hello All,
>
> test case 180 fails often (4 out of 5) in my x86_64 system.
> Any suggestions on how to proceed to debug ?
I have been seeing failures like that sometimes
(more often recently I think) for a while. I
have not had the chance to really chase it down.
If you can reproduce it pretty relibly you could
use "git bisect" to try to find out whether the
failures started to occur after a particular
commit.
-Alex
> regards,
>
> chandra
>
> 80 176s ... - output mismatch (see 180.out.bad)^M
> --- 180.out 2011-04-20 08:34:36.000000000 -0700^M
> +++ 180.out.bad 2011-06-03 14:10:45.000000000 -0700^M
> @@ -1 +1,4 @@^M
> QA output created by 180^M
> +file /mnt/xfsScratchMntPt/656 has incorrect size - sync failed^M
> +file /mnt/xfsScratchMntPt/818 has incorrect size - sync failed^M
> +file /mnt/xfsScratchMntPt/899 has incorrect size - sync failed^M
> Ran: 180^M
> Failures: 180^M
> Failed 1 of 1 tests^M
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-16 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 18:51 xfstests test case 180 fails often Chandra Seetharaman
2011-06-16 21:29 ` Alex Elder [this message]
2011-06-28 23:39 ` Chandra Seetharaman
2011-06-29 1:04 ` Dave Chinner
2011-06-29 21:54 ` Chandra Seetharaman
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=1308259762.2717.31.camel@doink \
--to=aelder@sgi.com \
--cc=sekharan@us.ibm.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