Re: [Xen-devel] Xen project CI systems and committer workflow

[Ian Jackson <ian.jackson@xxxxxxxxxx>]

This all sounds good.

Wei Liu writes ("Xen project CI systems and committer workflow"):
> ## Gaps
> 
> The component / system which merges trees and drives CI systems is missing.
> 
> Patchew and Patchwork don't do all the things we care about yet.

We need to decide how the plumbing should be arranged.

> ## Concerns
> 
> For individual committers, turnaround time may become longer since
> you need to wait for other trees to be processed.

This will probably be worth it.

A problem we identified in IRL discussion is that currently we rely
rather too much on osstest retesting the same tree, because of
heisenbugs.  With the new scheme it would spend more of its time
testing things which would never be retested.  So I think in your
`gaps' we need this:

  osstest facility to automatically retry failing tests

(This feels like admitting defeat but I have occasionally had a
campaign of trying to squash heisenbugs and it is *really hard work*.
I doubt we can get rid of them completely.)

> Gitlab CI doesn't have a self pushgate. If it is broken by accident Osstest
> will be blocked.

Could we plan some kind of procedural or robotic workaround ?

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel