Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume

[Sergio Durigan Junior <sergiodj@redhat.com>]

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.  </pie in the sky>.

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/