From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 43001 invoked by alias); 15 Jan 2018 20:11:40 -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 42878 invoked by uid 89); 15 Jan 2018 20:11:32 -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= 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 20:11:30 +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 2A78980469; Mon, 15 Jan 2018 20:10:56 +0000 (UTC) Received: from localhost (unused-10-15-17-193.yyz.redhat.com [10.15.17.193]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D87FB608E0; Mon, 15 Jan 2018 20:10:55 +0000 (UTC) From: Sergio Durigan Junior To: Pedro Alves Cc: Edjunior Machado , Yao Qi , Andreas Arnez , GDB Patches , David Edelsohn , Edjunior Machado Subject: Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume References: <7eccd434-6f47-590e-e53f-32076e99c98b@redhat.com> <8c13014a-5ff1-db52-03b4-995d300e9248@redhat.com> Date: Mon, 15 Jan 2018 20:11:00 -0000 In-Reply-To: <8c13014a-5ff1-db52-03b4-995d300e9248@redhat.com> (Pedro Alves's message of "Mon, 15 Jan 2018 18:17:09 +0000") Message-ID: <87h8rm6fxs.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-01/txt/msg00279.txt.bz2 On Monday, January 15 2018, Pedro Alves wrote: > 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. I'll see about that. There must be a way, because the web interface provides this information, but I don't remember seeing it before. > Ideally we'd even get a notification if time jumped > seemingly too much between builds. This would take more time to implement, but if there is a way to obtain the build time, then it should be possible. > 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. . I'll leave this pie in the sky :-). -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/