xfs
[Top] [All Lists]

Re: WANTED: xfstests results in different architectures

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: WANTED: xfstests results in different architectures
From: Phil White <pwhite@xxxxxxx>
Date: Tue, 18 Jun 2013 19:05:41 -0700
Cc: Chandra Seetharaman <sekharan@xxxxxxxxxx>, XFS mailing list <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20130618233426.GD29338@dastard>
References: <1371596399.22504.38.camel@xxxxxxxxxxxxxxxxxx> <20130618233426.GD29338@dastard>
User-agent: Mutt/1.5.21 (2010-09-15)
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

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