Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Implement timestamp'ed output on "make check"
Date: Wed, 05 Dec 2018 20:26:00 -0000	[thread overview]
Message-ID: <87efavbu02.fsf@redhat.com> (raw)
In-Reply-To: <87sgzbohzb.fsf@linux.vnet.ibm.com> (Pedro Franco de Carvalho's	message of "Wed, 05 Dec 2018 18:07:20 -0200")

On Wednesday, December 05 2018, Pedro Franco de Carvalho wrote:

> Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
>> From my recollection, ISTR that the gdbserver builders were *very* slow
>> even before this commit.  I was even talking to Edjunior about disabling
>> the gdbserver builders, because they were just contributing to making
>> the queue larger for the native builder.
>
> It seems they were taking about one hour before, at least on the LE
> builders, although I think the BE ones were taking longer.  Is one hour
> more than expected for the gdbserver builders?  If not, I'll see if I
> can figure out what's taking long.

Hm, on the native builder (CentOS-ppc64le-m64), the builds were taking
about 30 minutes.  However, on
CentOS-ppc64le-native-extended-gdbserver-m64 and
CentOS-ppc64le-native-gdbserver-m64, the builds were taking much
longer.  For example:

  https://gdb-build.sergiodj.net/builders/CentOS-ppc64le-native-gdbserver-m64/builds/1988
  Elapsed	6 hrs, 30 mins, 12 secs

  https://gdb-build.sergiodj.net/builders/CentOS-ppc64le-native-gdbserver-m64/builds/1997
  Elapsed	20 hrs, 52 mins, 15 secs

Things get much worse with native-extended:

  https://gdb-build.sergiodj.net/builders/CentOS-ppc64le-native-extended-gdbserver-m64/builds/1992
  Elapsed	37 hrs, 4 mins, 29 secs

  https://gdb-build.sergiodj.net/builders/CentOS-ppc64le-native-extended-gdbserver-m64/builds/1988
  Elapsed	37 hrs, 6 mins, 19 secs

Unfortunately they haven't reached the commit which introduces the
timestamp feature, so we still don't know exactly where they're hanging.

>> Alright.  I'll try to cancel the builds up until
>> 80e24d09860dbeba7d435b4a4f0990f85dbc084e and see how things go.
>>
>> Thanks for taking the time to investigate this!
>
> Thank you!

No problem.

I've now cancelled the builds; let's see how things go.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  parent reply	other threads:[~2018-12-05 20:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 22:12 Sergio Durigan Junior
2018-11-23 14:42 ` Alan Hayward
2018-11-23 15:03 ` [PATCH v2] " Sergio Durigan Junior
2018-11-23 18:23   ` Simon Marchi
2018-11-25 16:24     ` Sergio Durigan Junior
2018-11-25 19:56       ` Simon Marchi
2018-11-25 23:23         ` Sergio Durigan Junior
2018-11-26  0:47           ` Simon Marchi
2018-11-26 16:29             ` Sergio Durigan Junior
2018-11-26 17:22               ` Simon Marchi
2018-11-26 18:48           ` Sergio Durigan Junior
2018-12-05 19:39 ` [PATCH] " Pedro Franco de Carvalho
2018-12-05 19:48   ` Sergio Durigan Junior
     [not found]     ` <87sgzbohzb.fsf@linux.vnet.ibm.com>
2018-12-05 20:26       ` Sergio Durigan Junior [this message]
2018-12-06 15:30         ` Pedro Alves
2018-12-06 15:54           ` Pedro Alves
2018-12-06 19:32             ` Pedro Franco de Carvalho
2018-12-06 19:52               ` Sergio Durigan Junior
2018-12-07 20:06                 ` Pedro Alves
2018-12-07 22:09                   ` Sergio Durigan Junior
2018-12-08 12:58                     ` Pedro Alves
2018-12-08 23:16                       ` Sergio Durigan Junior
2018-12-09  8:57                         ` Philippe Waroquiers
2018-12-06 19:41         ` Pedro Franco de Carvalho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87efavbu02.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedromfc@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox