[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] automation: Creating a patchwork instance to improve pre-commit build testing

On 24/07/2018, 11:19, "Wei Liu" <wei.liu2@xxxxxxxxxx> wrote:
    On Tue, Jul 24, 2018 at 04:04:05AM -0600, Jan Beulich wrote:
    > I'm afraid my personal bar for any such automation is pretty
    > high: There must not ever be any negative effect from such an
    > addition. Positive effects would of course be very welcome. I
    > realize this is an unrealistic goal, but it should at least come
    > close (perhaps after some initial learning phase). But this implies
    > that at least in theory it is possible to come close in the first
    > place, which I can't take for given with the information I've been
    > provided so far.
    Then I'm afraid the only suggestion I get for you at the moment is to
    add a filter to dump those emails to /dev/null -- you already realised
    that's an unrealistic goal (at least at the beginning).
First of all, there should only be mail (aka spam) if there was a failure. 

Hopefully such failures will be fairly rare in the long term: as people 
learn that  they are expected to submit patches that build on all 
platforms, one  would expect that they test this *before* submitting 

And maybe we can gradually phase this in: aka have the contributor 
add something like CC xengit-testbot@xxxxxxxxxxxxxx to the series.
At some point later, we could always trigger a CI build. Or we could 
add a tag in the subject line, e.g. [CI-TESTED PATCH ...] or something 
like it, which triggers the test run.

Maybe it would also be possible that contributors can send patches
to xengit-testbot@xxxxxxxxxxxxxx without CC'ing xen-devel
to test whether their patches would pass the CI test. Or provide 
some alternative to doing so. 


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.