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 7E7853858D33; Sun, 1 May 2022 16:37:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7E7853858D33 Received: by gnu.wildebeest.org (Postfix, from userid 1000) id 7EB43302BBED; Sun, 1 May 2022 18:37:34 +0200 (CEST) Date: Sun, 1 May 2022 18:37:34 +0200 From: Mark Wielaard To: binutils@sourceware.org Cc: Overseers mailing list , Thomas Fitzsimmons , Dan =?iso-8859-1?Q?Hor=E1k?= , "Frank Ch. Eigler" Subject: binutils builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Message-ID: <20220501163734.GA30898@gnu.wildebeest.org> References: <5c1f217a-109c-2973-6c69-abf412133dee@arm.com> <524b04b7-a78c-7aae-4605-b40f61e6830c@arm.com> <16fe426d-c436-f030-dc43-0e81e7f0e853@arm.com> <20220428141957.GB23335@gnu.wildebeest.org> <20220428162803.GD23335@gnu.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220428162803.GD23335@gnu.wildebeest.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-3.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.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2022 16:37:37 -0000 Hi binutils hackers (dropped gdb), https://builder.sourceware.org now has 6 binutils builders: https://builder.sourceware.org/buildbot/#/builders?tags=binutils debian-amd64, fedora-x86_64, fedora-s390x, debian-ppc64, debian-armhf and debian-arm64. I like to add a fedora-ppc64le one once that one has enough disk space. The first two are configured with --enable-targets=all. The others not because they are too slow and/or --enable-targets=all causes extra failures. All build all-gas all-ld all-bintuils all-gold fine. fedora-x86_64 and binutils-debian-ppc64 pass the whole testsuite check-gas check-ld check-binutils. The gas and binutils testsuites seem clean on all builders. But the ld testsuite does see some unexpected failures or passes on some builders. It would be great if we could fix these. If not it might make sense to run the ld testsuite separately. Note that you can see the used linux kernel, gcc, binutils versions on the workers page: https://builder.sourceware.org/buildbot/#/workers binutils-fedora-s390x https://builder.sourceware.org/buildbot/#/builders/binutils-fedora-s390x has 2 unexpected ld failures: FAIL: Run pr19719 fun undefined FAIL: pr26580-3 binutils-debian-amd64 https://builder.sourceware.org/buildbot/#/builders/binutils-debian-amd64 has 2 unexpected ld failures: FAIL: Run p_align-1b with PIE FAIL: Run p_align-1d with -Wl,-z,max-page-size=0x1000 with PIE binutils-debian-arm64 https://builder.sourceware.org/buildbot/#/builders/binutils-debian-arm64 has 1 unexpected success: XPASS: Run pr19719 fun undefined binutils-debian-armhf https://builder.sourceware.org/buildbot/#/builders/binutils-debian-armhf has 8 unexpected ld failures and 7 unexpected successes XPASS: Run pr19719 fun undefined FAIL: Common symbol override ifunc test 1a FAIL: Common symbol override ifunc test 1b FAIL: Run pr18841 with libpr18841b.so FAIL: Run pr18841 with libpr18841c.so FAIL: Run pr18841 with libpr18841bn.so (-z now) FAIL: Run pr18841 with libpr18841cn.so (-z now) FAIL: Run pr23169a FAIL: Run pr23169d XPASS: visibility (hidden_undef) (non PIC) XPASS: visibility (hidden_undef) (non PIC, load offset) XPASS: visibility (hidden_undef) (PIC main, non PIC so) XPASS: visibility (protected_undef) (non PIC) XPASS: visibility (protected_undef) (non PIC, load offset) XPASS: visibility (protected_undef) (PIC main, non PIC so) The binutils-debian-armhf builder is also the slowest (takes 15 minutes). The rest take a few minutes. They should sent email once a new failure occurs (or if one if the currently failing builders starts passing). There is also one build and check everything builder https://builder.sourceware.org/buildbot/#/builders/binutils-gdb-fedrawhide-x86_64 I haven't looked at the test results yet, but they are all stored in the bunsendb.git for later analysis. This builder doesn't sent emails on bad builds. It also takes a very long time to run (from 1 to 7 hours). Cheers, Mark