|
From: Nicholas N. <n.n...@gm...> - 2023-03-23 08:51:15
|
Nice, I wasn't aware of any of those facilities. Are they documented anywhere, both their existence and how to use them? I couldn't find anything on valgrind.org about them, but maybe I overlooked something. Nick On Thu, 23 Mar 2023 at 19:45, Mark Wielaard <ma...@kl...> wrote: > Hi Nick, > > On Thu, Mar 23, 2023 at 07:31:47AM +1100, Nicholas Nethercote wrote: > > Thanks to Paul and Mark for a couple of small fixes to my commit. > > Thank you for the big fixes/rewrite! > > > Yesterday I was idly dreaming about the quality-of-life improvements that > > would be available if Valgrind was hosted on GitHub: > > - ability to upload commits ahead of time, in a fashion nicer than > "attach > > patch to bugzilla" > > - ability to do reviews > > - CI support for pre-merge testing runs > > - easier entry for newcomers > > > > Does sourceware.org have support for any of these things? > > Yes, sourceware offers patchwork.sourceware.org (in combination with > public-inbox support) which can be used for patch tracking and can be > configured to do pre-commit CI. And through builder.sourceware.org you > can do builds for "try branches". > > Note that valgrind already is using the sourceware CI for arm64, > armhf, i386, ppc64, ppc64le, power10, power9, x86_64 on some gnu/linux > distros: > https://builder.sourceware.org/buildbot/#/builders?tags=valgrind > > And there are of course the nightly builders which report to > valgrind-testresults: > https://sourceforge.net/p/valgrind/mailman/valgrind-testresults/ > > We have been pondering moving bugzilla and the mailinglists to > sourceware so we can have better integration (for example to > automatically link bugs, patches and commits). But weren't sure those > improvements were enough to "break" old links/habits. > > Cheers, > > Mark > |