linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Figg <brad.figg@canonical.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Ubuntu Ext4 regression testing
Date: Wed, 12 Sep 2012 19:04:18 -0700	[thread overview]
Message-ID: <50513F22.3040201@canonical.com> (raw)
In-Reply-To: <50513C1A.9020504@redhat.com>

On 09/12/2012 06:51 PM, Eric Sandeen wrote:
> On 9/12/12 7:41 PM, Brad Figg wrote:
> 
>> Eric,
>>
>> Thanks for taking the time to point this out. We will adjust our testing accordingly.
>> We initially tried to run xfstest against ext2, ext3, ext4, xfs and btrfs. We are also
>> trying to get these tests to run on several different kernel versions as you can
>> see from our test results. We were running into issues on different kernels and various
>> file-systems while getting our act together, we did this as a band-aid.
> 
> I see.
> 
>> I accept that we have some things to learn w.r.t. running this test suite. We will work
>> to run the xfstests "as is" without any outside "intelligence". We do recognise that
>> is a dynamic set of tests that people are adding to regularly.
>>
>> I am not attempting to get just a series of "pass" results. If that were my goal
>> I could accomplish it much easier and would not have engaged with the community
>> on the mailing list. We want to help where we can and will accept constructive
>> criticism.
> 
> Sorry, it sounds like I came across too strong there - it was just a little worrying to see failing or problematic tests disabled or otherwise artificially restricted.
> 
> I'm actually very excited to see you setting up ongoing, public testing using xfstests, I think it'll be a great benefit, especially if there's a way to see a particular test's results across several kernel versions and/or filesystems and/or architectures, so that patterns of failure can emerge.
> 
> If you find that xfstests is missing some feature or behavior which would facilitate testing in the automated environment, please do let us know what you need - or send patches.  :)
> 
> Thanks,
> -Eric
> 
>> Brad
>>
> 

No harm, no foul. We really don't mind constructive criticism. We are also
eager to get this setup and running. We will try to contribute more than
just running tests.

I do want to point out that we are using the xfstests which is a snapshot
in autotest. We do also look at the latest xfstests in the official xfstests
repo and add it in when we see a delta. We will also work with the autotest
maintainers to stay more up-to-date with xfstests.

Thanks,
Brad
-- 
Brad Figg brad.figg@canonical.com http://www.canonical.com

  reply	other threads:[~2012-09-13  2:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 22:52 Ubuntu Ext4 regression testing Brad Figg
2012-09-12 23:01 ` Eric Sandeen
2012-09-12 23:15   ` Brad Figg
2012-09-13  0:20     ` Eric Sandeen
2012-09-13  0:41       ` Brad Figg
2012-09-13  1:51         ` Eric Sandeen
2012-09-13  2:04           ` Brad Figg [this message]
2012-09-13  2:09             ` Eric Sandeen
2012-09-13  2:17               ` Brad Figg
2012-09-13  2:24               ` Theodore Ts'o
2012-09-13  2:18 ` Theodore Ts'o
2012-09-13  2:50   ` Brad Figg
2012-09-19  3:41     ` Theodore Ts'o

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=50513F22.3040201@canonical.com \
    --to=brad.figg@canonical.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).