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 EAE723833786; Sun, 26 Jun 2022 22:23:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EAE723833786 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 (deer0x0e.wildebeest.org [172.31.17.144]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 34E1B30005B6; Mon, 27 Jun 2022 00:23:55 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id BBEBF2E83312; Mon, 27 Jun 2022 00:23:55 +0200 (CEST) Date: Mon, 27 Jun 2022 00:23:55 +0200 From: Mark Wielaard To: libc-alpha@sourceware.org Cc: buildbot@sourceware.org Subject: glibc builder.sourceware.org integration Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-5.6 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: Sun, 26 Jun 2022 22:24:01 -0000 Hi, We have a shared buildbot for all Sourceware and GNU Toolchain projects: https://builder.sourceware.org/ There are a couple of glibc builders now: https://builder.sourceware.org/buildbot/#/builders?tags=glibc The compile-only builders, glibc-debian-i386, glibc-debian-ppc64, glibc-fedora-ppc64le, glibc-fedora-s390x, glibc-opensuseleap-x86_64 and glibc-opensusetw-x86_64 are all green. The builds are pretty quick (using ccache) and take a couple of minutes at most. So they run on each separate commit to the master branch. It currently doesn't include arm64 and armhf builds, but those could be added (the current boards are somewhat slow, but we will hopefully get some faster hardware soon). email notification of build failures hasn't been setup up yet. When we set it up should it also notify the libc-alpha mailing list when a build failure is detected? Only the first build failure will sent an email till the build is restored. There are currently two builders which do a make && make check. glibc-fedora-x86_64 and glibc-fedrawhide-x86_64. The first is a container build of fedora-latest (f36). The second is a fedora rawhide VM. The container builder has a couple of failures for which I just sent patches. With those patches the build should turn green. At which point we can also use it to detect test regressions. Doing a full make && make check in the container takes ~15 to ~20 minutes and so isn't don't on every individual build, but batches up changes till there have been none for 10 minutes. So it won't run behind. It should detect a commit that caused a regression within 30 minutes. All test results (including all .out files) are uploaded into the bunsendb for analysis: https://builder.sourceware.org/testruns/?has_keyvalue_like_k=testrun.git_describe&has_keyvalue_like_v=%25glibc%25 Not all hardware is powerful enough to do a full make check on every commit. But it would be good to make them do some real tests and not just do a compile-only run. Is there a good, small, quick, sub-test that could be added? gdb and binutils are experimenting with git user try branches so they can do pre-commit checking: https://sourceware.org/pipermail/binutils/2022-June/121293.html We can setup the same for glibc. Which we then can use for patchwork integration. Next week we should get more hardware and we can setup more full builders for different configurations. Please contact buildbot@sourceware.org with ideas and/or to help out with the setup (which is in a public git repo, see the builder project homepage). Cheers, Mark