All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: OSSTEST: Re-blessing cubietruck-{picasso, gleizes, metzinger} for production use
Date: Wed, 20 Jan 2016 11:58:36 +0000	[thread overview]
Message-ID: <1453291116.26343.79.camel@citrix.com> (raw)
In-Reply-To: <22175.29921.14605.696939@mariner.uk.xensource.com>

On Wed, 2016-01-20 at 11:52 +0000, Ian Jackson wrote:
> Ian Campbell writes ("OSSTEST: Re-blessing cubietruck-
> {picasso,gleizes,metzinger} for production use"):
> > I've been running a couple of adhoc production tests per day on these
> > since
> > before Xmas and they haven't lost sight of their disks again.
> > 
> > TLDR; I think we should throw them back in the pool.
> 
> Great.

I'll take this as a "yes, go ahead" ;-)

> > With the recent timeout fixes they are working as well as the
> > production
> > cubietruck-braque.
> > 
> > There are two flakey tests test-armhf-armhf-xl-rtds and test-armhf-
> > armhf-
> > libvirt-raw, but those appear to be much better than before the timeout
> > changes and not specific to these three boards since the fourth one
> > looks
> > to behave much the same.
> > 
> > At first glance it looks like some later test steps might just need a
> > bit
> > more time on CT too.
> 
> Maybe we should have target_adjust_timeout honour a host property to
> multiply timeouts by some factor.

That's not a bad idea, assuming the remaining issues really are timeouts of
this sort.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-01-20 11:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 10:53 OSSTEST: Re-blessing cubietruck-{picasso, gleizes, metzinger} for production use Ian Campbell
2016-01-20 11:52 ` Ian Jackson
2016-01-20 11:58   ` Ian Campbell [this message]
2016-01-20 12:28     ` Ian Campbell
2016-01-20 16:16     ` Ian Campbell
2016-01-20 16:56     ` Ian Campbell
2016-01-20 17:13       ` Ian Jackson

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=1453291116.26343.79.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.