distributed tests of a patch

Damien Lespiau damien.lespiau at intel.com
Tue Aug 25 23:30:30 AEST 2015

On Tue, Aug 25, 2015 at 03:06:09PM +0200, Thomas Monjalon wrote:
> 2015-08-19 11:33, Damien Lespiau:
> > patchwork know about series first though, otherwise I don't think it
> > makes much sense to test patches in isolation.
> I think it makes sense to test every patches in a series.
> Though I agree we need a simple method to apply previous patches of the series.

Precisely, testing every patch of a series or not (sure, you'd want to
test every patch if it's practical), one still needs to know what
constitute a series. I can hopefully have an RFC ready in the next
couple of weeks.

> A series id could help.

Yup, part of the plan, like patches have ids today. In my mind at least,
the series id is unique, even across revisions of that series (ie
v2/v3/... of the whole series or resend-ing an individual patch after
review comments).

Just like patches today as well, they would have a unique URL ie.


Which could be left as a tag in the commit message if people want to be
able to track the history of the commit (very much like the gerrit
Change-Id tags).


More information about the Patchwork mailing list