On Thu, 12 Nov 2020 23:25:22 -0300 Marcelo Ricardo Leitner wrote: > On Thu, Nov 12, 2020 at 02:20:58PM -0800, Jakub Kicinski wrote: > > On Thu, 12 Nov 2020 11:24:57 +0800 we...@ucloud.cn wrote: > > > v7-v10: fix __rcu warning > > > > Are you reposting stuff just to get it build tested? > > > > This is absolutely unacceptable. > > I don't know if that's the case, but maybe we could have a shadow > mailing list just for that? So that bots would monitor and would run > (almost) the same tests are they do here. Then when patches are posted > here, a list that people actually subscribe, they are already more > ready. The bots would have to email an "ok" as well, but that's > implementation detail already. Not that developers shouldn't test > before posting, but the bots are already doing some tests that may be > beyond of what one can think of testing before posting.
The code for the entire system is right here: https://github.com/kuba-moo/nipa It depends on a patchwork instance to report results to. I have a script there to feed patches in locally from a maildir but haven't tested that in a while so it's probably broken. You can also just run the build bash script without running the whole bot: https://github.com/kuba-moo/nipa/blob/master/tests/patch/build_allmodconfig_warn/build_allmodconfig.sh Hardly rocket science. I have no preference on what people do to test their code, and I'm happy to take patches for the bot, too. But we can't have people posting 11 versions of patches to netdev which is already too high traffic for people to follow. Not to mention that someone needs to pay for the CPU cycles of the bot, and we don't want to block getting results for legitimate patches.
