From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id NL81HOBhpGpmUwEAWB0awg (envelope-from ) for ; Fri, 11 Sep 2026 16:17:36 -0400 Received: by simark.ca (Postfix, from userid 112) id 5EE701E09E; Fri, 11 Sep 2026 16:17:36 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.1 Received: from vm01.sourceware.org (vm01.sourceware.org [IPv6:2620:52:6:3111::32]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 59BE11E033 for ; Fri, 11 Sep 2026 16:17:35 -0400 (EDT) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id CB1DA48FE54A for ; Fri, 11 Sep 2026 20:17:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CB1DA48FE54A Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 55414485137B; Fri, 11 Sep 2026 20:16:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 55414485137B 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 55414485137B Authentication-Results: sourceware.org; arc=none smtp.remote-ip=45.83.234.184 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1789157761; cv=none; b=I6YxAzGfC3VjP+CyvyKU1SWCnPzc1wt0wobgyom3xFKkF1ext6xWX5QjD0WKNvlCB7X2ilSHXW80DpgtGjlx6OUiBDDw2Y9Wa+LRp/Yv5fTA1WR63ZvXKpncrl0AQWQmiT6ZD5fFuK1YYCqpIm83LCsQdU1u3fdrdz2YUZzHH4k= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1789157761; c=relaxed/simple; bh=JpvD8HWJ2wnBgl0fLII8rpmjwHbsrFyMd0w82Jw8BhA=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=fwwuKdPQe0/0Kmf/bgOIUT+xnjtpIouc/GI9nKs+/47KQraCMBWKPN3yeew4xdzBjzA/T7xvmJAzUy3rU4UpWSkH7yHn/AiLgobn+3slipOJiSusjqzl5geK4vQmwGg9D588IFOL29YztxZ/rC/8oEUNgsnKQNjrt5D4SoZiBBM= ARC-Authentication-Results: i=1; sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 55414485137B Received: by gnu.wildebeest.org (Postfix, from userid 1000) id 44D7432D7E95; Fri, 11 Sep 2026 22:16:00 +0200 (CEST) Date: Fri, 11 Sep 2026 22:16:00 +0200 From: Mark Wielaard To: overseers@sourceware.org Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org, binutils@sourceware.org, gdb@sourceware.org Subject: Re: Sourceware - Building Together, Fri 11, 15:00 UTC Message-ID: <20260911201600.GO23490@gnu.wildebeest.org> References: <8bf28f40d7dad5169cdd0b222f38ec903a718d90.camel@klomp.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8bf28f40d7dad5169cdd0b222f38ec903a718d90.camel@klomp.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hi, On Thu, Sep 10, 2026 at 01:58:41PM +0200, Mark Wielaard wrote: > Discussion topics about various CI builder buildbots/patchwork/etc: For those that couldn't attend. Some notes on the topics discussed. - The sware-gg-bot in #overseers that grants unlimited https access has been moved to #sourceware-goodguys. The 429 error page has been updated if you still happen to see those. Joining the #overseers-goodguys channel directly from your host, without a "cloak", should automatically but temporarily remediate. - Claudio fixed the syncing of the gcc-wwwdocs repo (the bot was not allowed to push to the gcc- wwwdocs repo) Also forge-stage has been updated to the latest forgejo release. > - Rainer would like to extend the Solaris (amd64 and sparcv9) > buildbot workers to gdb > https://inbox.sourceware.org/ydd4iglf9yj.fsf@CeBiTec.Uni-Bielefeld.DE This would reuse the workers already setup for binutils. And the tricky 32bit-only case if off the table. Also disabling sim and no targets=all. Only PATH differs. make check-gdb is clean on solaris? It really only matters for the reporting, if we have a clear/clean "green" list we can immediately sent out warning emails Most other builders use a curated list of tests to run that are known to not fail. See https://sourceware.org/cgit/builder/tree/builder/master.cfg#n3752 We'll integrate it with the full make check-gdb list, but disable fail email reporting for now. Then we'll review the results and see whether or not to configure the mail reporter. - A buildbot related question for gcc folks. A vendor of build services (incredibuild) has offered free buildbot/build services to the sourceware fleet, and has an interest in supporting the gcc project specifically. They'd welcome suggestions as to architecture, configuration, target sorts of triplets we should configure for them. (We would not be running any of their software on sourceware or nearby; they'd be running build/tests on their own hw/sw as a community donor). Please let fche and/or buildbot@sourceware.org know of any suggestions or concerns. Richard suggested looking into glibc's scripts/build-many-glibcs.py > - DJ would like to run the patchwork CI/CD curator in a Sourceware VM > https://sourceware.org/glibc/wiki/CICDDesign > https://gitlab.com/djdelorie/glibc-cicd > This is also a good opportunity to discuss putting patchwork as a > whole in its own isolated VM. And to see if we can use some of the > builder servers/VM to use the curator to do CI builds. > https://sourceware.org/sourceware-wiki/servers-and-services-2026/ Agreed on https://patchwork.sourceware.org/cicd/curator.cgi as canonical URL. This must be stable because runners will connect to it. It can be a simple single-url proxy from an apache server to a hidden internal curator instance. The curator is one python script that runs four or so processes and talks to mariadb. It can run anywhere. mjw would like to take this oppertunity to create a new patchwork VM and stuff everything in there. We already reserved space for it 4 vcores, 12GB mem, 30GB disk (double checked that is enough). But some pushback to that and some discussion about whether to run in containers instead and the maintenance cost of each option. In the end decided it really is three separate tasks. That shouldn't be handled in one big bang. So for now we'll simply would be to have it isolated as separate user on vm01 (possibly in its own container). After that works we can see about additional steps and/or a separate VM. For the trybots (buildbots) it is suggesting that they run on "corporate branded" hardware as advertisement for other companies to donate more hardware (or run their own). There is a collection of those here https://builder.sourceware.org/#thanks:~:text=Thanks > - Should we look into bugspray? A public-inbox bugzilla integrator: > https://git.kernel.org/pub/scm/utils/bugspray Yes, but time ran out. > - An update on funding https://sourceware.org/financials.html Numbers for Augustus, $400+ private donations that month, still have to see how much of that is recurring. The first Supply Chain Defender corporate sponsor Open Source Security, Inc. $5000 has been fully processed. Others still in progress, vacations, purchase orders, other processes take a lot of time. > - Builders/CI talk at Cauldron with tips and tricks for having all > our automated processes (buildbots, try-bots, pre/post-commit-CI/CD, > snapshots, forgejo runners, patchwork's curator, etc.) working smoothly, > even in the face of the AI scraperbot attacks, and how to add your own. > https://conf.gnu-tools-cauldron.org/prg26/talk/review/YZDVBNFDPSSZERNAYRYDCS8XWF3BURZC > The FSF (GNU Toolchain projects fiscal sponsor) and SFC > (Sourceware fiscal sponsor) will also attend to answer any > questions on how we are running the community infrastructure > together with our other partners. All the above give some good input into what might be interesting to talk about.