From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <dunlapg@umich.edu>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: osstest "short fast" tests of xen-unstable proposal
Date: Fri, 3 Jul 2015 09:51:56 +0200 [thread overview]
Message-ID: <1435909916.14347.55.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZajGJbThtD-ZGA7S_Uw5nizTw0j38E7MTxaY8CwS7LsAA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1539 bytes --]
On Thu, 2015-07-02 at 18:17 +0100, George Dunlap wrote:
> On Tue, Jun 30, 2015 at 6:46 PM, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> > Invent a new `xen-unstable-smoke' flight (in osstest terminology, a
> > `branch').
> >
> > This would be a push gate for xen.git. Its input would be
> > xen.git#staging. Its output would be a new branch, xen.git#smoked.
> > The existing `xen-unstable' flights would take xen.git#smoked as
> > input. So there would be a two-stage push gate,
> >
> > staging -[xen-unstable-smoke test]-> smoked -[xen-unstable test]-> master
> >
> > This would apply to xen-unstable only, not to stable braches, nor to
> > any other codebase (eg, qemu or Linux). It would aim to run every 2h.
> >
> > Arrangements would be made to reuse the outputs of most recent builds
> > of qemuu and the currently favoured Linux branch.[5]
> >
> > If any test failed, the flight would be automatically aborted and
> > report immediately [6]. Unlike most flights, tests would not be
> > `sticky' to failing hosts, nor (when succeding) prefer hosts which
> > they hadn't run on for a while [6], so they would take the first
> > available machine.
>
> This sounds good to me.
>
+1
This would all be really, really useful!
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-03 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 17:46 osstest "short fast" tests of xen-unstable proposal Ian Jackson
2015-07-02 17:17 ` George Dunlap
2015-07-03 7:51 ` Dario Faggioli [this message]
2015-07-06 15:41 ` Jan Beulich
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=1435909916.14347.55.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dunlapg@umich.edu \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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.