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 0798D385AC3F for ; Tue, 12 Dec 2023 09:40:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0798D385AC3F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 0798D385AC3F Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=45.83.234.184 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702374052; cv=none; b=lM5XBaUtBXQgIOpI331Yiz+k5PH+7TXuqpKghH4tgxzWjB0IV3M9GnApN6x2A7cbcbsUHjnbUeGFZFsFN30O9wR+a4qyg7F7XpJ0Gz02Zr7ng2lLwkq5cg2yXBMSsuIcO9fy77H3pMX3m3M4mgB20zRclOi9WKp/6N3OAOApPlM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702374052; c=relaxed/simple; bh=3AQXQ56YViqD4gfDlzlXb4Wmb2GFD6fApHTMtBOlNSw=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=IJ3uRjma3uE7TMduVTG4sI/CJ0hhM9ATqe923CtSPTJBwIc7ly4HCRdxta5pPeXWienNDz31aBHR7TM/q74j8odRTVpUXJuB8dNxhYmutBiuoRAdPmuEWDc9Ps9zGB8lZHXJuufJs2Re4TVyNY5G62OdrTGVToyTgkwYwbtDXls= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by gnu.wildebeest.org (Postfix, from userid 1000) id 1547A302FDCD; Tue, 12 Dec 2023 10:40:50 +0100 (CET) Date: Tue, 12 Dec 2023 10:40:50 +0100 From: Mark Wielaard To: Rainer Orth Cc: Simon Marchi , gdb-patches@sourceware.org, Simon Marchi Subject: Re: [COMMITTED PATCH] Fix procfs.c compilation Message-ID: <20231212094050.GD14917@gnu.wildebeest.org> References: <20231210230701.GB14917@gnu.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE 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 Rainer, On Mon, Dec 11, 2023 at 03:40:20PM +0100, Rainer Orth wrote: > > On Fri, Dec 01, 2023 at 11:09:36AM +0100, Rainer Orth wrote: > >> >> Btw., I'd considered reviving the Solaris buildbots to guard against > >> >> this kind of issues. However, they'd both (sparcv9 and amd64) would > >> >> need to be build-only: the make check phase takes 3-5 times as long as > >> >> the build, there are about 2500 failures and quite a number of those are > >> >> flakey. I have no idea if the new buildmaster allows for such a > >> >> compile-only configuration, though (the previous one did). > >> > >> > Having build-only builders would already be really great, I'm pretty > >> > sure it's possible (CCing Mark Wielaard). > >> > >> I think I checked when the new buildmaster went first online, but > >> couldn't find anything at the time. I've now rechecked the new config > >> and indeed there are quite a number of build-only configs in use. > > > > We do have workers for different architectures, but they are all > > GNU/Linux. If you have a Solaris worker that can be used then please > > contact https://sourceware.org/mailman/listinfo/buildbot > > I do: both systems (Solaris 11.4/SPARC and Solaris 11.4/amd64) used to > run compile-only buildbots with the previous buildmaster. > > They are currently used for LLVM (sparcv9, amd64) and Golang (amd64) > buildbots, but have some free capacity. Lets discuss on the buildbot mailinglist how we can hook those up if you want to. > >> > If you can identify a few simple and stable tests, it's possible to run > >> > just those (I think that's what the buildbot does even for Linux/x86 > >> > today). It would at least help ensure that GDB is not completely > >> > broken. > >> > >> Seems like a good compromise between a pure build-only config and one > >> that runs the full testsuite, but drowns us in noise from timeouts and > >> flakiness. I'll have a look. > > > > Currently the list of tests run for gdb is fairly small, but they are > > all must succeed tests (they are run under native, gdbserver and > > extended-gdbserver): > > https://sourceware.org/cgit/builder/tree/builder/master.cfg#n2883 > > I'll check if those work reliably. In the worst case, the Solaris bots > would have to become compile-only, so at least guarding against build > failures. However, I'm uncertain about gdbserver: I don't even know if > it compiles on Solaris, let alone does anything useful. We can be very flexible in what we build/test. It doesn't need to be the same set of tests, we can remove gdbserver build/tests for Solaris, etc. We can do builds on every commit, collapse builds for the last set of commit or just once a day. Cheers, Mark