From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 38531 invoked by alias); 15 Jan 2018 18:17:18 -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 38481 invoked by uid 89); 15 Jan 2018 18:17:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=gdb-testers, gdbtesters, hang 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; Mon, 15 Jan 2018 18:17:16 +0000 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D977237E8E; Mon, 15 Jan 2018 18:17:14 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4A349600D2; Mon, 15 Jan 2018 18:17:10 +0000 (UTC) Subject: Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume To: Edjunior Machado , Yao Qi References: <7eccd434-6f47-590e-e53f-32076e99c98b@redhat.com> Cc: Andreas Arnez , Sergio Durigan Junior , GDB Patches , David Edelsohn , Edjunior Machado From: Pedro Alves Message-ID: <8c13014a-5ff1-db52-03b4-995d300e9248@redhat.com> Date: Mon, 15 Jan 2018 18:17:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-01/txt/msg00278.txt.bz2 On 01/15/2018 05:37 PM, Edjunior Machado wrote: > (FWIW, at first glance, gdb.linespec/cpcompletion.exp in ppc64 BE seems to > be one of the main culprits for the whole testrun taking longer (~1h) and > with considerably more failures than in ppc64le, aparently due to the > ppc64's function descriptor.) Sergio, would it possible to include the time it took to run the testsuite in the messages sent to gdb-testers? As is, such new long cascading timeouts are introduced without one realizing, unless you go look at the builds' pages one by one. Ideally we'd even get a notification if time jumped seemingly too much between builds. And IWBN if the gdb buildbot web frontend had some kind of graph tracking/plotting test run duration over time (build# for a given builder), so we could just open some URL and notice the spikes. . Thanks, Pedro Alves