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 3C9523858C51; Tue, 21 Jun 2022 17:30:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3C9523858C51 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 tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id C801E30006B1; Tue, 21 Jun 2022 19:30:01 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 567D64045497; Tue, 21 Jun 2022 19:30:01 +0200 (CEST) Message-ID: <60db1ab53cd9e65c9c22b11bbfd5706ebcc85a90.camel@klomp.org> Subject: Re: buildbot users try branch builders From: Mark Wielaard To: Szabolcs Nagy Cc: binutils@sourceware.org, gdb@sourceware.org, buildbot@sourceware.org, Thomas Fitzsimmons , fche@redhat.com Date: Tue, 21 Jun 2022 19:30:01 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-5.2 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 X-BeenThere: buildbot@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "The https://builder.sourceware.org/ buildbot" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2022 17:30:04 -0000 Hi Szabolcs, On Tue, 2022-06-21 at 11:30 +0100, Szabolcs Nagy wrote: > The 06/20/2022 12:48, Mark Wielaard wrote: > > The armhf and arm64 builders have left out for now since they are a > > bit too slow. We'll hopefully get a 8 core Ampare machine from the > > Oregon State University this week so we can also enable those arm > > builders. >=20 > what is the requirement for the machine? i have an aarch64 machine > for public gnu tools ci, and i can set up build slaves there if > there are instructions how to do it. The requirements are not that big, in theory that tinker-board and odroid-board are fine as buildbot-workers. But only for smaller builds. To actually run some of the larger builds it should have at least 8GB and 4cpus. More is better of course. Especially for the larger projects if you want to do full test runs and not just "quick" CI builds. Disk again depends on how many builds/projects you want to support. It is really beneficial to have a bigger ~5GB ccache for repeat builds. binutils takes ~2G (plus another ~2G for the try builder), similar for gdb and libabigail, gccrust is ~4.5G, valgrind ~600MB, elfutils ~300MB, bzip2, dwz are just a couple of MB. If we want to add glibc and enable try builders for more projects I estimate 30GB to 50GB. The gccrust builder does just a --disable-bootstrap build, so a full gcc builder would add another 10G at least (maybe 2 or 3 times if we want to add try builders). If you like to do container builds then those are almost full distros, so add at least another 4GB per container/distro type (we currently support 4). So you can get away with ~15GB, but might need up to ~300GB if you want to do more and larger builds across multiple distros. There is a little documentation on adding workers (they used to be called slaves, but buildbot renamed them some time ago) in the README: https://sourceware.org/git/?p=3Dbuilder.git;a=3Dblob;f=3DREADME;hb=3DHEAD#l= 111 But that is mostly from the side of the buildbot master. The easiest setup is one with a dedicated distro install with a buildbot-worker:=20 https://docs.buildbot.net/current/manual/installation/worker.html All you really need to do is make sure a full distro is installed with all development packages. You can take a peek at one of the container files to see which:=20 https://sourceware.org/git/?p=3Dbuilder.git;a=3Dtree;f=3Dbuilder/containers= ;hb=3DHEAD Then create a user which can run the buildbot-worker. Please contact the buildbot@sourceware.org mailinglist for connection info. Another way is making sure you have docker installed (podman sadly seems incompatible at the moment) and a builder user that is in the docker group which can be accessed through ssh to create full container images. But that is a bit more work (and currently depends on some specific user uid to make in/out container sharing easier). Please again contact the buildbot@sourceware.org mailinglist for more info. There are several people on the list who have setup buildbot-workers who can help. And then we can coordinate which projects/builders you want to support. https://sourceware.org/mailman/listinfo/buildbot Cheers, Mark