Hi Richard, I hope you had an enjoyable summer!
Picking up on this thread now, almost half a year later :) Sorry for the late reply but turned out (a little surprising) that I’m going to have a daughter soon which shifted my priorities a little… So, I looked into patchtest a few months ago and found a couple of issues where I considered a rewrite. So, I gave it a shot last weekend but instead of python I used rust. You can find the demo here: https://github.com/HerrMuellerluedenscheid/patchtest-rs The functionality is currently limited to loading a patch from the commandline, checking that the summary is in place and applying the patch to a repository given by a url. The repo will be cloned on the fly. The next step would be an smtp client that checks for incoming messages every N seconds and runs patchtest against patches and sends back a short report of what worked and what didn’t. I just wanted to check that revitalising patchtest is still an open issue and would like to ask for quick feedback. Best regards Marius > On 16. Apr 2022, at 18:35, Richard Purdie > <[email protected]> wrote: > > On Sat, 2022-04-16 at 17:15 +0200, Marius Kriegerowski wrote: >> Dear Richard, >> >> Thanks for the comprehensive answer! That helped me to get a better overview >> of >> what is there and how to proceed. >> >> I'll leave cosmetics for a later phase, stick to unittest and fix the >> integration so that we have a baseline from where to decide how to proceed. > > FYI I did notice some docs here: > > https://git.yoctoproject.org/patchtest/tree/usage.adoc > > Cheers, > > Richard >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1629): https://lists.openembedded.org/g/openembedded-architecture/message/1629 Mute This Topic: https://lists.openembedded.org/mt/88763351/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
