From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 47605 invoked by alias); 7 Sep 2017 19:32:53 -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 47591 invoked by uid 89); 7 Sep 2017 19:32:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=spamming, dear X-HELO: mail-oi0-f68.google.com Received: from mail-oi0-f68.google.com (HELO mail-oi0-f68.google.com) (209.85.218.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 07 Sep 2017 19:32:48 +0000 Received: by mail-oi0-f68.google.com with SMTP id z73so445674oia.0 for ; Thu, 07 Sep 2017 12:32:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=g13dW3oKXh7HWZNJ1F8/i+k5p0qQDYB9KB1PF9dqBYU=; b=mJTO5qSsLugYQWovPsfAJ10XamjXiEr1ztzHjruC1klC3YOGRJmXxkI/fhTdA6hx1t dpR6J3882BROTPn34avl4F03ayU4TRWYJ8CgZQ6IRNe5kNDKiwQdfXl1rY1qSCQDPmNO G6S+5uHcPaTdcjUiWlYCc36E+Z4nB2GdwDLnOeRwlBlgWayZyvChnyI1XF0bptfjzuCC 2L58oVQ1m/d34SktNyVWOlnbFU943QId7IBMdEjiWGZSpTvB4NHc5rKR4tw6Yjn7RPqE X1/+ZUqgll/GR5V/YDC+kM0dNMKbdzh5cH9ytaw9XQcMboK+fdoz2zn0xd6lTUnmI2Bj 3hXQ== X-Gm-Message-State: AHPjjUgPz3hEcyYkNdWppIeKz9A54iWt54Qbi0zRd5ge6BuvsbfwJP8a MRe2MntJO0P1ahbBUlt/ZWmY6x6cXnvt X-Google-Smtp-Source: AOwi7QBZqJU67/vya9UN+qyztE4KEV8XhXPfs0RoCyjOQ3n8U+Sbr8FfIDC/lts05XeUaEmnZ1edVs25b1DnUOT3wXg= X-Received: by 10.202.102.25 with SMTP id a25mr396010oic.301.1504812766270; Thu, 07 Sep 2017 12:32:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.136.75 with HTTP; Thu, 7 Sep 2017 12:32:45 -0700 (PDT) In-Reply-To: <87efritk02.fsf@redhat.com> References: <87efritk02.fsf@redhat.com> From: "H.J. Lu" Date: Thu, 07 Sep 2017 19:32:00 -0000 Message-ID: Subject: Re: Oh dear. I regret to inform you that commit b1308d2c3749cc454f00b70768ee33724d919527 might be unfortunate To: Sergio Durigan Junior Cc: Palmer Dabbelt , GDB Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00190.txt.bz2 On Thu, Sep 7, 2017 at 11:57 AM, Sergio Durigan Junior wrote: > 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. > Does it build for a target for any new commits which are unrelated to the target? For example, when I make some changes to bfd/elfxx-x86.h, will it triggers a gdb build for Sparc? -- H.J.