fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 00/15] xfstests: remove IRIX support
Date: Mon, 24 Jul 2017 10:38:15 -0700	[thread overview]
Message-ID: <20170724173815.GB143373@gmail.com> (raw)
In-Reply-To: <20170724044308.GB9167@eguan.usersys.redhat.com>

On Mon, Jul 24, 2017 at 12:43:08PM +0800, Eryu Guan wrote:
> On Thu, Jul 20, 2017 at 09:38:38PM -0700, Eric Biggers wrote:
> > Hello,
> > 
> > This is v2 of the patchset to remove IRIX support from xfstests.  For
> > some time xfstests has de facto not supported IRIX anymore.  The final
> > release of IRIX was over 10 years ago and it seems no one has been
> > running the latest xfstests releases on any IRIX system, as at the very
> > least xfstests now assumes the existence of some util-linux binaries.
> > There are very likely other examples of this bitrot as well.  Also,
> > xfsprogs has already dropped IRIX support.
> > 
> > Therefore, this patchset simplifies things by removing IRIX support from
> > the xfstests tests, build system, and documentation.  It also ports the
> > useful IRIX-specific tests to Linux.  Of course, people will still find
> > more cruft later to remove, but this should be a good start.
> > 
> > To get around the mailing list message size limit, the series is
> > formatted with --irreversible-delete.  Therefore it can't be applied
> > directly.  It can be retrieved from git here:
> > https://github.com/ebiggers/xfstests.git, branch remove_irix_support_v2.
> 
> Great work! Thank you so much for doing this! I pulled & merged your
> branch into a test branch and am running some tests now, overall it
> looks good to me.
> 
> Though, as you mentioned, there're some places that could do further
> cleanups (e.g. I'm wondering if we can kill _supported_os completely and
> remove it from 'new' template, and some $HOSTOS and $PKG_PLATFORM checks
> could be cleaned up too), I agree this is a great start. Thanks again!
> 

We shouldn't make it too hard to port xfstests to other platforms in the future,
but yes I think at least _supported_os and $HOSTOS should probably go, since
they're subject to bitrot and checking the OS isn't usually what is really
wanted anyway.  Really we should check for the presence of some feature,
program, quirk, etc. instead, instead of being lazy and checking for "Linux".

Eric

      reply	other threads:[~2017-07-24 17:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21  4:38 [PATCH v2 00/15] xfstests: remove IRIX support Eric Biggers
2017-07-21  4:38 ` [PATCH v2 01/15] tests: port generic/093 to Linux Eric Biggers
2017-07-21  4:38 ` [PATCH v2 02/15] tests: port generic/097 " Eric Biggers
2017-07-21  4:38 ` [PATCH v2 03/15] tests: port xfs/095 " Eric Biggers
2017-07-21  4:38 ` [PATCH v2 04/15] tests: remove udf/098 Eric Biggers
2017-07-21  4:38 ` [PATCH v2 05/15] tests: remove udf/101 Eric Biggers
2017-07-21  4:38 ` [PATCH v2 06/15] tests: remove xfs/114 and xfs/115 Eric Biggers
2017-07-21  4:38 ` [PATCH v2 07/15] tests: remove xfs/057 and xfs/058 Eric Biggers
2017-07-21  4:38 ` [PATCH v2 08/15] tests: remove generic/099 Eric Biggers
2017-07-21  4:38 ` [PATCH v2 09/15] tests: make shared/051 a generic test Eric Biggers
2017-07-21  4:38 ` [PATCH v2 10/15] README: remove IRIX-specific documentation Eric Biggers
2017-07-21  4:38 ` [PATCH v2 11/15] tests: remove IRIX support from tests also supported on Linux Eric Biggers
2017-07-21  4:38 ` [PATCH v2 12/15] tests: clean up per-OS output files Eric Biggers
2017-07-21  4:38 ` [PATCH v2 13/15] common: remove IRIX-specific code Eric Biggers
2017-07-28 11:19   ` Eryu Guan
2017-07-28 16:50     ` Eric Biggers
2017-07-21  4:38 ` [PATCH v2 14/15] build: remove IRIX-specific build logic Eric Biggers
2017-07-21  4:38 ` [PATCH v2 15/15] include: remove some unused headers Eric Biggers
2017-07-24  4:43 ` [PATCH v2 00/15] xfstests: remove IRIX support Eryu Guan
2017-07-24 17:38   ` Eric Biggers [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=20170724173815.GB143373@gmail.com \
    --to=ebiggers3@gmail.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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).