xfs
[Top] [All Lists]

Re: [Lsf] [PATCH] xfstests-bld: Simplify determination of number of CPUs

To: Eric Sandeen <sandeen@xxxxxxxxxx>
Subject: Re: [Lsf] [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all
From: Theodore Ts'o <tytso@xxxxxxx>
Date: Thu, 3 Apr 2014 15:30:40 -0400
Cc: Andy Lutomirski <luto@xxxxxxxxxxxxxx>, LukÃÅ Czerner <lczerner@xxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, lsf@xxxxxxxxxxxxxxxxxxxxxxxxxx, Linux FS Devel <linux-fsdevel@xxxxxxxxxxxxxxx>, Sedat Dilek <sedat.dilek@xxxxxxxxx>, "linux-ext4@xxxxxxxxxxxxxxx" <linux-ext4@xxxxxxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1396553440; bh=w5NsyIio3ZcL24j5kEfU9d9W2Vh/HWT7VIdunQ5o0qs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=SLXN/0sWKgKxVimoR6AOgcI94IJSs0esLxYshLGIfl6aIgkQKN8ANusgXohqaLSgd RjZ1sWNwYaH37c0YIQYrcd+j1tiwj3YdIQWRCsAFQXKwWiaku+3E3qJ078ygi5YxbT uCmrwZ/jpeM+L6I8kTiEALGF/ozcGIAHNH0K2wTQ=
In-reply-to: <533DB140.8010103@xxxxxxxxxx>
References: <20140328161806.GA31772@xxxxxxxxx> <20140331025148.GF16336@dastard> <20140401023711.GE4911@xxxxxxxxx> <20140401222823.GJ17603@dastard> <20140402142620.GA6901@xxxxxxxxx> <20140403011411.GL16336@dastard> <alpine.LFD.2.00.1404031102310.2124@xxxxxxxxxxxxxxxxxxxxx> <CALCETrU=JWigDSv6ymepS2tjL+EkO98VDC03-RSPuhQVk3yvZA@xxxxxxxxxxxxxx> <20140403173504.GB23737@xxxxxxxxx> <533DB140.8010103@xxxxxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)
On Thu, Apr 03, 2014 at 01:06:40PM -0600, Eric Sandeen wrote:
> On 4/3/14, 11:35 AM, Theodore Ts'o wrote:
> 
> >>  - There's an undocumented way to write results outside the source
> >> tree called RESULT_BASE.  It would be great if it were documented and
> >> spelled consistently.
> 
> I'm not actually certain that it was intended to be used this way.
> See 1686f9ab "xfstests: Introduce a results directory" 
> which explains just where this variable came from and what it's
> for...

The last paragraph states of the git description states:

    This is the first (small) step in being able to store test results
    in an external location for archival/data mining purposes.

The question I suppose is whether storing the results in an external
location is something that should be xfstests' responsibility, or of
the test harnesses that call xfstests.  I suspect that since there are
so many different ways people might want to archive the results, it
does make sense for the test harnesses to handle this job, but I
wouldn't want to "presume" on anything that the xfstests developers
might choose to do....

                                                - Ted

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