From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 622BF3858D20; Wed, 9 Nov 2022 10:18:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 622BF3858D20 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x0b.wildebeest.org [172.31.17.141]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 6CCF83045FB4; Wed, 9 Nov 2022 11:18:49 +0100 (CET) Received: by reform (Postfix, from userid 1000) id E389C2E8368D; Wed, 9 Nov 2022 11:18:48 +0100 (CET) Date: Wed, 9 Nov 2022 11:18:48 +0100 From: Mark Wielaard To: Richard Biener Cc: Sam James , Joseph Myers , Martin =?utf-8?B?TGnFoWth?= , Jakub Jelinek , Xi Ruoyao , Sandra Loosemore , GCC Patches , GCC Development Subject: Re: Announcement: Porting the Docs to Sphinx - tomorrow Message-ID: References: <7bae16bc-9069-4964-a80e-7ebff82e007e@suse.cz> <2a4347ab-40a1-2afc-f48c-6d8290afb7c6@suse.cz> <2ab60531-23fd-9a27-c84c-4948b79bc84a@suse.cz> <6931CA90-0DC7-492D-9AEA-82D8FA45E0B7@gentoo.org> <591A3B5E-C707-4A20-8A4E-EF5B7F73ED56@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-3032.9 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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 > wrote: > > > On 9 Nov 2022, at 00:00, Joseph Myers 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