On Fri, 2018-11-09 at 00:42 +1100, Daniel Axtens wrote: > Hi Christopher, > > > What I'm really trying to is get to the point where the series can be > > tested. I know you've written and talked about using Patchwork for this > > [1]. > > You might want to check out snowpatch [1], it does this sort of thing at > the moment and is live on linuxppc-dev mailing list. For example here's > some links of it running tests against patches and series sent to the > list: > > - https://patchwork.ozlabs.org/patch/994798/ (early patch in series, 2 > tests run - does it apply and does it pass style-checks) > > - https://patchwork.ozlabs.org/patch/994810/ (final patch in series, 6 > tests run including 4 build-tests) > > - https://patchwork.ozlabs.org/patch/993734/ (standalone patch, 6 tests run) > > AIUI, it's a very similar concept to Stephen's blog post (pw + jenkins), > but it's all wrapped up nicely for you.
I was going to suggest this but after looking through the code I saw references to concepts from thefreedesktop-fork like TestResult (called Checks in upstream) and series revisions [1]. Does this definitely work against upstream, yeah? Stephen [1] https://github.com/ruscur/snowpatch/blob/8e93b453ad/src/patchwork.rs#L176-L204 > Regards, > Daniel > > [1]: https://github.com/ruscur/snowpatch _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
