From: Theodore Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
xfs@oss.sgi.com, lsf@lists.linux-foundation.org,
"Sedat Dilek" <sedat.dilek@gmail.com>,
"Linux FS Devel" <linux-fsdevel@vger.kernel.org>,
"Lukáš Czerner" <lczerner@redhat.com>,
"Andy Lutomirski" <luto@amacapital.net>
Subject: Re: [Lsf] [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all
Date: Thu, 3 Apr 2014 15:30:40 -0400 [thread overview]
Message-ID: <20140403193039.GD32323@thunk.org> (raw)
In-Reply-To: <533DB140.8010103@redhat.com>
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
next prev parent reply other threads:[~2014-04-03 19:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 9:03 [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all Sedat Dilek
2014-03-28 16:18 ` tytso
2014-03-29 10:04 ` Sedat Dilek
2014-03-29 14:04 ` Theodore Ts'o
2014-03-31 2:51 ` [Lsf] " Dave Chinner
2014-04-01 2:37 ` Theodore Ts'o
2014-04-01 2:37 ` Theodore Ts'o
2014-04-01 22:28 ` Dave Chinner
2014-04-01 22:28 ` Dave Chinner
2014-04-02 14:26 ` Theodore Ts'o
2014-04-03 1:14 ` Dave Chinner
2014-04-03 1:14 ` Dave Chinner
2014-04-03 10:26 ` Lukáš Czerner
2014-04-03 17:05 ` Andy Lutomirski
2014-04-03 17:35 ` Theodore Ts'o
2014-04-03 17:35 ` Theodore Ts'o
2014-04-03 17:42 ` Andy Lutomirski
2014-04-03 17:42 ` Andy Lutomirski
2014-04-03 19:06 ` Eric Sandeen
2014-04-03 19:06 ` Eric Sandeen
2014-04-03 19:21 ` Andy Lutomirski
2014-04-03 19:21 ` Andy Lutomirski
2014-04-03 21:46 ` Eric Sandeen
2014-04-03 19:30 ` Theodore Ts'o [this message]
2014-04-03 21:20 ` Dave Chinner
2014-04-03 13:16 ` Mel Gorman
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=20140403193039.GD32323@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf@lists.linux-foundation.org \
--cc=luto@amacapital.net \
--cc=sandeen@redhat.com \
--cc=sedat.dilek@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.