Re: [Xen-devel] osstest "short fast" tests of xen-unstable proposal

[George Dunlap <dunlapg@xxxxxxxxx>]

On Tue, Jun 30, 2015 at 6:46 PM, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> osstest's test coverage is improving, which means that the tests keep
> taking longer.  Even with ongoing expansion of the test facility, the
> overall time between a bad push and getting results can be quite long
> - currently perhaps 12-36h depending on circumstances.
>
> It would be better if we could get quicker notification of build
> breakages and other kinds of very basic breakage.
>
> I propose:
>
>
> 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.

 -George

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