On Fri, 14 Dec 2018, Jeff Law wrote: > > I wonder if we could set up auto-(simulator)-testing for all supported > > archs (and build testing for all supported configs) on the CF > > (with the required scripting in contrib/ so it's easy to replicate). I'd > > simply test only released snapshots to keep the load reasonable > > and besides posting to gcc-testresults also post testresults > > differences to gcc-regression? > It's certainly possible. Though I've found that managing this kind of > thing with Jenkins is far easier than rolling our own. I'd be happy to > move an instance out into the CF.
On the other hand, in glibc having a single script build-many-glibcs.py that does everything (rather than some external piece of software to orchestrate builds) serves to make it easy for people making changes with cross-architecture risks to run the compilation tests for all architectures - although doing so is slow unless you have lots of CPU cores. -- Joseph S. Myers jos...@codesourcery.com
