From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 92482 invoked by alias); 25 Oct 2018 16:26:21 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 92446 invoked by uid 89); 25 Oct 2018 16:26:19 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=weekend, gdb-testers, sneak, H*f:sk:5862fa9 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 25 Oct 2018 16:26:18 +0000 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E560DC025D15; Thu, 25 Oct 2018 16:26:16 +0000 (UTC) Received: from localhost (unused-10-15-17-196.yyz.redhat.com [10.15.17.196]) by smtp.corp.redhat.com (Postfix) with ESMTP id 99912608EC; Thu, 25 Oct 2018 16:26:16 +0000 (UTC) From: Sergio Durigan Junior To: Alan Hayward Cc: Ramana Radhakrishnan , Simon Marchi , GDB Patches , Simon Marchi , nd , Pedro Alves Subject: Re: Status of the AArch* builders References: <20180606151629.36602-1-alan.hayward@arm.com> <5862fa9c22cc48d86256686e74d60f20@polymtl.ca> <82743c0795488492486076685b9f8828@polymtl.ca> <93f7cb8434f463508b3fc3cfbcd29ef0@polymtl.ca> <877en43qx1.fsf@redhat.com> <644470E6-AEB8-4F84-890C-7496EC8BB419@arm.com> <8736xr4ukx.fsf@redhat.com> <6b1500d9-bc31-aa09-586f-d451b910d880@foss.arm.com> <7BC78EF8-06BE-439B-835B-0F0847BF785F@arm.com> <877ejf50qo.fsf_-_@redhat.com> <87a7o7ot6r.fsf@redhat.com> <355AA6DE-FAB1-425B-8CE2-6E1508E57F88@arm.com> <87ftxb6l3u.fsf@redhat.com> <87zhvf4c0y.fsf@redhat.com> <87va63444j.fsf@redhat.com> <87lg6wxvh4.fsf@redhat.com> <4A72ED8A-E9AC-479F-B7FF-0C3638FB296A@arm.com> Date: Thu, 25 Oct 2018 16:26:00 -0000 In-Reply-To: <4A72ED8A-E9AC-479F-B7FF-0C3638FB296A@arm.com> (Alan Hayward's message of "Wed, 24 Oct 2018 09:56:08 +0000") Message-ID: <87va5qdmc7.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-10/txt/msg00585.txt.bz2 On Wednesday, October 24 2018, Alan Hayward wrote: >> On 17 Oct 2018, at 19:45, Sergio Durigan Junior wr= ote: >>=20 >>> For now, I have disabled the email notifications. IME there's always >>> something that we need to tweak in the first days to make sure that the >>> builders are running fine. So if you could just keep an eye on the >>> builds and make sure that everything is OK, I'd appreciate. >>>=20 >>> After a few days have passed, I will enable the email notifications. >>> Regular test failures will be sent to the gdb-testers@ ml, and breakages >>> will be sent to gdb-patches@. >>=20 >> For the record, I've now enabled the e-mail notifications for the >> Aarch64 builders. I've also added them to the list of Try builders, so >> it's possible to submit try jobs to them. >>=20 > > Currently the AArch64 builders keep going back to failed regressions. Thi= s is > mostly due to *all* the gdb.threads and gdb.server tests being racy on AA= rch64 > Ubuntu. Keeping it down to 16 threads has reduced the frequency, but not > removed it. > I=E2=80=99m currently trying to fix up as many of the AArch64 test failur= es across the > whole test suite as I can. I suspect fixing the threaded issue is going to > take a while longer. TBH, all builders suffer from this problem. They all have racy tests, and even though I tried to implement a system to detect such tests and exclude them from the reports that are sent to gdb-testers, they still sneak in the reports. That's the main (and sole?) reason why gdb-testers is currently impossible to follow, and people don't really read it. > In the meantime is it possible to update just the AArch64 buildbot script= s so > they don=E2=80=99t take into account the thread/server tests for regressi= ons? Either > remove the tests before running, or grep them out of the results. Not sur= e if > that=E2=80=99s possible with the way it=E2=80=99s set up (and not sure wh= ere to look). This > would then give us confidence with the rest of the tests. They can be > reinstated when stable again. I think it can be done, but it's not so trivial, and I'm busy with other stuff right now :-/. Sorry about that. I'll try to take a look at this problem during the weekend. BTW, the configuration files for the GDB BuildBot live at: https://git.sergiodj.net/gdb-buildbot.git/ Thanks, --=20 Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/