All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Manish Aggarwal <mani.iitb@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: auto group failing on kernel v2.6.38.5
Date: Thu, 16 Jun 2011 09:46:53 -0500	[thread overview]
Message-ID: <4DFA175D.9060005@sandeen.net> (raw)
In-Reply-To: <BANLkTimmEHrxONk-bm354sPnnLyc-0eQ-w@mail.gmail.com>

On 6/16/11 12:05 AM, Manish Aggarwal wrote:
> Hi Eric,
> 
> Thanks for responding. Yes I agree most of the Test Cases are failed
> due to the umount failure.
> 
> But isn't the "quick and auto" group are supposed to run without any
> error?

Yes, but if that were guaranteed, there would be no reason to run them!  :)

> The point is in case I am running xfstest suite on some target, how
> would I know that whether the there is some error with my target (or
> kernel settings) or if there is some error in xfs test suite itself.

The test suite is not perfect; it evolves, and there are bugs in it
as with any other software.

It is your role as a developer and as a user of the test suite to
investigate failures, and discern where the problem lies.

In general, the test suite works.  Busy filesystems at unmount are
not a common result, so you need to try to find out why you are
running into that, and what the root cause may be ...

Running on a usb stick is not something the core xfs developers do,
so you may well run into unique issues.

-Eric

> Regards, Manish

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2011-06-16 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  9:24 auto group failing on kernel v2.6.38.5 Manish Aggarwal
2011-06-15 14:59 ` ***** SUSPECTED SPAM ***** " Dave Chinner
2011-06-15 15:03 ` Eric Sandeen
     [not found]   ` <BANLkTimmEHrxONk-bm354sPnnLyc-0eQ-w@mail.gmail.com>
2011-06-16 14:46     ` Eric Sandeen [this message]

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=4DFA175D.9060005@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=mani.iitb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.