Hi, On Wed, Nov 09, 2022 at 08:49:22AM +0100, Richard Biener via Gcc wrote: > On Wed, Nov 9, 2022 at 1:09 AM Sam James via Gcc-patches > <gcc-patc...@gcc.gnu.org> wrote: > > > On 9 Nov 2022, at 00:00, Joseph Myers <jos...@codesourcery.com> wrote: > > > On Tue, 8 Nov 2022, Sam James via Gcc wrote: > > > > If that's your expectation, that's fine, but I'd regard it as pretty > > serious if one didn't build, and I don't remember a time when it didn't. > > > > It's not like it's that much use if it fails to build on a bog-standard > > amd64 platform anyway, as if nothing else, you'd get a deluge > > of duplicate bug reports. > > I'd say that doing a trunk snapshot build every day as CI would be nice, we > can then publish one once a week, skipping days where the build failed. > > For release branches having generated files in the snapshots would be > even more useful and I very much hope the build there always succeeds.
The current buildbot CI jobs already run various builds which just do a simple non-bootstrap build (plus some that do a full build and make check) to see if things work: https://builder.sourceware.org/buildbot/#/builders?tags=gcc&tags=gcc-full If we make sure the relevant machine/containers contain the necessary prerequirements then can add the configure flags to some builders to make sure the docs are generated: https://sourceware.org/git/?p=builder.git;a=blob;f=README And make it sent warning emails (to gcc-testresults) when things break. Cheers, Mark
