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 BA4913858C2C; Fri, 29 Apr 2022 20:04:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BA4913858C2C 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: by gnu.wildebeest.org (Postfix, from userid 1000) id AF5E8302BBED; Fri, 29 Apr 2022 22:04:22 +0200 (CEST) Date: Fri, 29 Apr 2022 22:04:22 +0200 From: Mark Wielaard To: "gdb@sourceware.org" Cc: Overseers mailing list , Thomas Fitzsimmons , Dan =?iso-8859-1?Q?Hor=E1k?= , "Frank Ch. Eigler" Subject: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Message-ID: <20220429200422.GB7305@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=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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 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: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2022 20:04:25 -0000 Hi gdb hackers (dropped binutils), https://builder.sourceware.org now has 6 build only builders. centos-x86_64, fedora-x86_64, debian-armhf, debian-arm64, fedora-s390x and debian-ppc64. I like to add a fedora-ppc64le one once that one has enough disk space. These builders are fairly quick, a few minutes at most. And all except the fedora-s390x one build fine. They should sent email once a new failure occurs. The fedora-s390x failure looks as follows: https://builder.sourceware.org/buildbot/#/builders/gdb-fedora-s390x In file included from /usr/include/c++/11/string:40, from ../../binutils-gdb/gdb/../gdbsupport/ptid.h:36, from ../../binutils-gdb/gdb/../gdbsupport/common-defs.h:198, from ../../binutils-gdb/gdb/defs.h:28, from ../../binutils-gdb/gdb/debuginfod-support.c:19: In static member function ‘static constexpr const char_type* std::char_traits::find(const char_type*, std::size_t, const char_type&)’, inlined from ‘constexpr std::basic_string_view<_CharT, _Traits>::size_type std::basic_string_view<_CharT, _Traits>::find(_CharT, std::basic_string_view<_CharT, _Traits>::size_type) const [with _CharT = char; _Traits = std::char_traits]’ at /usr/include/c++/11/bits/string_view.tcc:87:41, inlined from ‘constexpr std::basic_string_view<_CharT, _Traits>::size_type std::basic_string_view<_CharT, _Traits>::find_first_of(_CharT, std::basic_string_view<_CharT, _Traits>::size_type) const [with _CharT = char; _Traits = std::char_traits]’ at /usr/include/c++/11/string_view:431:26, inlined from ‘bool debuginfod_is_enabled()’ at ../../binutils-gdb/gdb/debuginfod-support.c:194:33: /usr/include/c++/11/bits/char_traits.h:413:62: error: ‘void* __builtin_memchr(const void*, int, long unsigned int)’ specified bound 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Werror=stringop-overread] 413 | return static_cast(__builtin_memchr(__s, __a, __n)); | ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~ 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. One issue with the build-check-everything builder might be the widely varrying build times which range from 1 to 7 hours. Cheers, Mark