public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil White <pwhite@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Chandra Seetharaman <sekharan@us.ibm.com>,
	XFS mailing list <xfs@oss.sgi.com>
Subject: Re: WANTED: xfstests results in different architectures
Date: Tue, 18 Jun 2013 19:05:41 -0700	[thread overview]
Message-ID: <20130619020541.GG424@caliban.engr.sgi.com> (raw)
In-Reply-To: <20130618233426.GD29338@dastard>

On Wed, Jun 19, 2013 at 09:34:26AM +1000, Dave Chinner wrote:
> How are you going to filter and display them on xfs.org? Should the
> scripts to do this be part of xfstests?
> 
> FWIW, without a database of results that users can use to filter the
> test results themselves, it will become unmanageable very quickly...
> 
> BTW, from my notes from the 2012 LSFMM XFs get-together, there are
> these line items related to exactly this:
> 
> ----
>        - Public repository of test results so we can better track failures
>                 - Look into resurrecting old ASG xfstests results
>                   repository and web iquery interface (Ben)
>                 - host on oss.sgi.com.
>                 - script to run xfstests and produce publishable output (Ben)
> ----
> 
> Ben, did you ever start to look into this?

That became my work, not Ben's.

The current proposal is to gather architecture, distro, memory size, number of
procs, characteristics of the storage device (size, performance, type, xfs_info
output), xfsprogs version numbers, the time it takes for each test to run, the
date & time it was run, and the hostname of the system.

The plan was to output that information into a database which we could add
benchmark information into as well with an eye to detecting performance
regressions.

(I felt, for example, that the recent discussion of CRC work and CPU usage
could have been helped by that.)

The last stage was to write a script to upload test run data which oss would
be able to publish.

Some of that work is done.  I need to get back around to it.

-Phil

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-06-19  2:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 22:59 WANTED: xfstests results in different architectures Chandra Seetharaman
2013-06-18 23:34 ` Dave Chinner
2013-06-19  2:05   ` Phil White [this message]
2013-06-19 16:19   ` Ben Myers
2013-06-19 21:00   ` Chandra Seetharaman
2013-06-19 22:37     ` Ben Myers
2013-06-19 22:44       ` [RFC PATCH 1/3] xfstests: get some basic source tree info Ben Myers
2013-06-20  3:20         ` Eric Sandeen
2013-06-20  3:50           ` Dave Chinner
2013-06-20 17:03             ` Ben Myers
2013-06-19 22:46       ` [RFC PATCH 2/3] xfstests: use an intermediate check.log file Ben Myers
2013-06-19 22:49       ` [RFC PATCH 3/3] xfstests: upload test results Ben Myers

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=20130619020541.GG424@caliban.engr.sgi.com \
    --to=pwhite@sgi.com \
    --cc=david@fromorbit.com \
    --cc=sekharan@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox