public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: "Kaul, Yaniv" <Yaniv.Kaul@emc.com>,
	Eric Sandeen <sandeen@sandeen.net>,
	Eric Sandeen <esandeen@redhat.com>,
	fstests@vger.kernel.org, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Can't build RPM of xfstests
Date: Tue, 21 Oct 2014 10:57:19 +1100	[thread overview]
Message-ID: <20141020235719.GQ17506@dastard> (raw)
In-Reply-To: <CAGpXXZJ1A=Zq74KGveo5D=uAr6GTdA_1=DqXYwm2x9rG8ggDBA@mail.gmail.com>

On Mon, Oct 20, 2014 at 07:31:50PM -0400, Greg Freemyer wrote:
> --
> Greg Freemyer
> 
> 
> On Mon, Oct 20, 2014 at 7:08 PM, Dave Chinner <david@fromorbit.com> wrote:
> > On Mon, Oct 20, 2014 at 08:54:47AM -0500, Eric Sandeen wrote:
> >> On 10/20/14 6:55 AM, Greg Freemyer wrote:
> >>
> >> > Opensuse is building rpms of 1.1.1 so the build infrastructure isn't
> >> > too badly broken.  I don't know if they are following FHS, but I
> >> > doubt they use /opt.
> >>
> >> The build works fine, it's the "Makepkgs" that I think is a bit odd,
> >> at least for RPM packaging.
> >
> > It's just odd, regardless of what it is packaging.
> >
> >> Also, if we really want to encourage packaging, we should probably start
> >> sticking official version numbers on it.  "1.1.1" was tagged in Dec 2012,
> >> and there have been no "releases" since.
> >
> > There are more recent tags than that. There were some linux-v3.[6-8]
> > tags added when kernels v3.[6-8] we released. Those tags are
> > basically meaningless from a release perspective, though.
> >
> > As it is, for the purpose of the discussion I'll argue that we don't
> > need official release versions or tarballs and that anyone who needs
> > packages for xfstests is Doing it Wrong(tm).
> 
> A potential use case with openSUSE and why I "think" they packaged it
> is to include a subset of xfstest in there automated testing.

Sure - i'm just pointing out that you don't need RPM to do that -
git it just as good for deploying automated testing infrastructure
;)

....

> Notice for example that ext4 is a testsuite selection in the testsuite
> pull down.  I assume that testsuite uses xfstests to exercise ext4
> prior to an automated release of factory.
> 
> The 2014-10-17 build of a couple days ago is an example of a build
> that failed the ext4 testsuite:
> https://openqa.opensuse.org/tests/27955

That doesn't appear to anything to do with xfstests. It appears to
be a "can we install opensuse" installer test that happens to be run
on ext4. i.e. it's really product level testing (i.e. whether the
opensuse build worked) not whether the filesystem works as it's
supposed to.

> I don't see automated tests for xfs or btrfs which is a surprise since
> both of them are default filesystem choices for factory.  (btrfs is
> the default choice for / and xfs is the default for /home).

Seeing as it's not actually doing filesystem level testing, it
probably doesn't matter at all.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2014-10-20 23:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12  6:58 Can't build RPM of xfstests Kaul, Yaniv
2014-10-20  1:47 ` Dave Chinner
2014-10-20  3:35   ` Eric Sandeen
2014-10-20 11:55     ` Greg Freemyer
2014-10-20 13:54       ` Eric Sandeen
2014-10-20 23:08         ` Dave Chinner
2014-10-20 23:31           ` Greg Freemyer
2014-10-20 23:57             ` Dave Chinner [this message]
2014-10-21  3:15         ` Eryu Guan
2014-10-20 23:23       ` Eric Sandeen

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=20141020235719.GQ17506@dastard \
    --to=david@fromorbit.com \
    --cc=Yaniv.Kaul@emc.com \
    --cc=esandeen@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=greg.freemyer@gmail.com \
    --cc=sandeen@sandeen.net \
    --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