From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Fri, 04 Sep 2020 21:05:42 +0200 Subject: [Buildroot] More maintainers In-Reply-To: (Michael Nazzareno Trimarchi's message of "Fri, 4 Sep 2020 20:12:49 +0200") References: <20200827223956.7cb87050@windsurf.home> <20200829095023.GC14354@scaer> <638a9bc4-197f-931e-0795-2605ff734291@mind.be> <20200903182409.6b337059@windsurf.home> <87o8mlmoga.fsf@dell.be.48ers.dk> Message-ID: <87ft7xmkft.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Michael" == Michael Nazzareno Trimarchi writes: Hi, >> And why wouldn't you be able to do the same with the email based setup >> today? With tools like snowpatch (https://github.com/ruscur/snowpatch) or >> some basic scripting around the patchwork REST API nicely allows you to >> run (command line :P) tools whenever new patches are posted. >> > I think that we should explore using snowpatch. Problem is to have a setup > and some machines that can run the CI. Is there a cost to have this running? Yes, it would need to run somewhere. Given the machine ressources spent on the autobuilders and defconfigs/runtime tests already, we can probably find ressources for that as well. Perhaps osuosl can help? But before we can do that we would need to figure out exactly what tests to do and what to report back to the submitter, E.G. running check-package is trivial, but figuring out what build tests or what runtime tests to run less so. -- Bye, Peter Korsgaard