From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (Postfix) with ESMTP id F340629DF7 for ; Thu, 3 Apr 2014 14:30:48 -0500 (CDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay2.corp.sgi.com (Postfix) with ESMTP id DE0FF304059 for ; Thu, 3 Apr 2014 12:30:48 -0700 (PDT) Received: from imap.thunk.org (imap.thunk.org [74.207.234.97]) by cuda.sgi.com with ESMTP id 5q7YUe2XOSoRwr4o (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 03 Apr 2014 12:30:47 -0700 (PDT) Date: Thu, 3 Apr 2014 15:30:40 -0400 From: Theodore Ts'o Subject: Re: [Lsf] [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all Message-ID: <20140403193039.GD32323@thunk.org> References: <20140328161806.GA31772@thunk.org> <20140331025148.GF16336@dastard> <20140401023711.GE4911@thunk.org> <20140401222823.GJ17603@dastard> <20140402142620.GA6901@thunk.org> <20140403011411.GL16336@dastard> <20140403173504.GB23737@thunk.org> <533DB140.8010103@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <533DB140.8010103@redhat.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Eric Sandeen Cc: "linux-ext4@vger.kernel.org" , xfs@oss.sgi.com, lsf@lists.linux-foundation.org, Sedat Dilek , Linux FS Devel , =?utf-8?B?THVrw6HFoQ==?= Czerner , Andy Lutomirski 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 _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs