[Top] [All Lists]

Re: Can't build RPM of xfstests

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: Can't build RPM of xfstests
From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
Date: Mon, 20 Oct 2014 19:31:50 -0400
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, "Kaul, Yaniv" <Yaniv.Kaul@xxxxxxx>, Eric Sandeen <esandeen@xxxxxxxxxx>, fstests@xxxxxxxxxxxxxxx, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7Bt6ZlOu0Gvsy9EfARh1RF4noGMEf6eBEXlSszkQ5Ko=; b=d5N67EYjh1b+A6PI+vDE1rbAvg5uFjVsURNaGXj+HBh2iQxToIWNQ1bbsf4+PEt5iy zC9Gvx9F0j86u6W9mePiDSbBr6mOnMxSkpJ+m2j7SbENUp+A9bPMFgL3T9FuAmuzcQWD oNnY89yT+uzYoRltskvArQCnCnjP08HoopzDJIPOqjFsGODJBMzjz9zHQR3ZNTL/Z4B2 NhoL8kEdjoXGu0etpjkA7i35pxEOK+ZKqhlFc+auxQDG+KuKSBQDhizkB7ql7p8apE0Y acBsgmZdEwgsoBjrd/oehQVYG2brWpySk8XpNFYuYWVId1WDk0ztDJ/iX6W/2iLArVfL SV9g==
In-reply-to: <20141020230840.GP17506@dastard>
References: <648473255763364B961A02AC3BE1060D03C7940C13@xxxxxxxxxxxxxxxxxx> <20141020014750.GL7169@dastard> <54448313.7040602@xxxxxxxxxxx> <30CA1845-C213-49EA-8809-F1E7A98AE7F9@xxxxxxxxx> <54451427.9060306@xxxxxxxxxxx> <20141020230840.GP17506@dastard>
Greg Freemyer

On Mon, Oct 20, 2014 at 7:08 PM, Dave Chinner <david@xxxxxxxxxxxxx> 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.

As of the last 9 months openSUSE's "factory" release has adopted a
rolling release mechanism similar to rawhide, but possibly a little
more reliable.

Many submissions to factory (the rawhide equivalent) are pushed
through a ring of automated QA tests.

Separately on a daily basis the entire current factory release is
pushed through a series of automated QA tests.

If all QA tests pass, then a full factory snapshot is automatically
released for end-user incorporation.

My hope is that xfstests is packaged by openSUSE so it can easily be
incorporated into that series of automated tests.

If they are not yet doing that, then having xfstests packaged
simplifies the future incorporation of xfstests into the auto-QA

Overview: https://openqa.opensuse.org/tests/

Table of automated test results:

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:

The 2014-10-18 build on the otherhand worked:

It is interesting to look through the various screen shots captured by
the automated test system.

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).

Note: openSUSE still will do formal releases and the next one is
openSUSE 13.2 due out next month.  13.2 should be getting lots of
manual testing in addition to the automated QA testing.


<Prev in Thread] Current Thread [Next in Thread>