All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>, Sean Dague <sean@dague.net>
Subject: Re: Re: 3.0-testing Status
Date: Fri, 16 Sep 2005 09:23:51 -0500	[thread overview]
Message-ID: <20050916142351.GC8699@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32DE4B@liverpoolst.ad.cl.cam.ac.uk>

* Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> [2005-09-16 09:12]:
>  
> > > James/Tom/Andrew are still adding tests and improving the 
> > UI, but the 
> > > current scorecard is at:
> > > 
> > > http://xenbits.xensource.com/xenrt
> > > 
> > > A username/password is not required to see the test status of 
> > > currently shipping hardware platforms (only prototype or 
> > pre-release).
> > 
> > Looks great!  Any chance in getting the data exported via xml 
> > or the like? 
> > The GUI is pretty and all, but it overfills my screen in many 
> > directions and there is some data I'd like to consolodate out 
> > of it without having to write a screen scraper. :)
> 
> Sure, xml export would be nice, but lets get 3.0 out the door first...
> 
> The most immediate need is to have a larger set of typical queries on
> the front page e.g. "all results from changesets in the last 48h". We
> also need to get more machines on-line running nightly tests, and fill
> in some of the currently missing tests.

Is this something that developers can set up a machine or two to help
fill out machine configurations?  Any way to contribute to filling in
the missing tests?

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

      reply	other threads:[~2005-09-16 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 12:16 Re: 3.0-testing Status Ian Pratt
2005-09-16 14:23 ` Ryan Harper [this message]

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=20050916142351.GC8699@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=sean@dague.net \
    --cc=xen-devel@lists.xensource.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.