From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12417 invoked by alias); 7 Sep 2017 18:57:09 -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 11531 invoked by uid 89); 7 Sep 2017 18:57:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=spamming 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, 07 Sep 2017 18:57:03 +0000 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id B07988046E; Thu, 7 Sep 2017 18:57:02 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B07988046E Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=sergiodj@redhat.com Received: from localhost (unused-10-15-17-193.yyz.redhat.com [10.15.17.193]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8A12168D89; Thu, 7 Sep 2017 18:57:02 +0000 (UTC) From: Sergio Durigan Junior To: "H.J. Lu" Cc: Palmer Dabbelt , GDB Subject: Re: Oh dear. I regret to inform you that commit b1308d2c3749cc454f00b70768ee33724d919527 might be unfortunate References: Date: Thu, 07 Sep 2017 18:57:00 -0000 In-Reply-To: (H. J. Lu's message of "Thu, 7 Sep 2017 11:00:22 -0700") Message-ID: <87efritk02.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00189.txt.bz2 On Thursday, September 07 2017, H. J. Lu wrote: > On Thu, Sep 7, 2017 at 10:56 AM, Palmer Dabbelt wrote: >> I think this wasn't my commits, as it seems to be broken as of 63c99141deff >> ("remove QStartupWithShell entry from NEWS::Changes in GDB 7.11"). Also, I >> haven't touched anything in aarch64 GDB land >> >> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2745 >> >> I can't find any other mention of this on "gdb-patches", though I'm not a GDB >> maintainer (we don't have a RISC-V GDB port yet) so I had to poke around the >> archives and therefor may be missing something. According to here >> >> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64?numbuilds=400 >> >> This has been broken since 34d16ea2a144 ("gdb.base/commands.exp: Test >> loop_break and loop_continue in nested loops"), but that failure isn't relevant >> to this one as it's a test failure not a build failure. >> >> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2671 >> >> I poked around and there was at least one compilation failure in >> between the one I just got emailed about and the test failure above, caused by >> 7022349d5c86 ("Stop assuming no-debug-info functions return int"). >> >> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2673/steps/compile%20gdb/logs/stdio >> >> Given that there's two different failures in three commits and I'm pretty sure >> I didn't cause this bug, I don't want to dig through the rest of the history to >> figure out what's going on. This has been broken for a while, is everyone else >> just ignoring these messages? >> > > This bot is next to useless. I just ignore it. Funny, I have another opinion of what is really useless. > This bot shouldn't spam people when the new commit doesn't change > the old error. The bot is not spamming anyone, it had a bug in the way it used to determine whether the breakage email should be sent. The bug has been fixed now. These breakage e-mails have caught many issues over time, so I still think they're very useful. Of course, if the GDB community decides, I can take the bot down at any time. If this happens, I suposse you must have a really better solution for CI. Anyway, it's a work-in-progress and has a few drawbacks and limitations, but overall I think people are reasonably satisfied with it. -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/