Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
	GDB Patches <gdb-patches@sourceware.org>,
		Edjunior Machado <emachado@redhat.com>
Subject: Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders
Date: Fri, 15 Dec 2017 15:53:00 -0000	[thread overview]
Message-ID: <CAGWvnykwWnHYjhXH08LSgiyvxgEyaMVFp9GU0N+KBDsbgrbmwA@mail.gmail.com> (raw)
In-Reply-To: <edd14c5a-e4ae-20c4-878a-e37252a6348c@redhat.com>

On Fri, Dec 15, 2017 at 10:42 AM, Pedro Alves <palves@redhat.com> wrote:
> On 12/15/2017 03:06 PM, David Edelsohn wrote:
>
>> Third, the testsuite summaries that no one from the GDB community
>> monitored show that the testsuite runtime jumped from a relatively
>> short amount of time to over 9 hours for each run, which points to a
>> newly introduced problem in GDB or in the testsuite (timeouts?).
>
> That may well be.  Can you point at some representative builds,
> before/after the jump?

The testsuite runs for 6 minutes on RHEL7 s390x buildslave and 9 hours
on Debian Jessie s390x buildslave.

The Debian Jessie system also runs a Python buildslave without
problem.  The system has 4 virtual cpus and 16GB of memory, which
should be more than adequately sized.

Thanks, David


  reply	other threads:[~2017-12-15 15:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 13:45 Sergio Durigan Junior
2017-12-15 13:54 ` David Edelsohn
2017-12-15 14:20   ` Sergio Durigan Junior
2017-12-15 14:34     ` David Edelsohn
2017-12-15 14:48       ` Pedro Alves
2017-12-15 15:06         ` David Edelsohn
2017-12-15 15:43           ` Pedro Alves
2017-12-15 15:53             ` David Edelsohn [this message]
2017-12-15 16:20               ` Pedro Alves
2017-12-15 17:29                 ` David Edelsohn
2017-12-15 18:55                   ` David Edelsohn
2017-12-15 19:20                     ` Pedro Alves
2017-12-15 23:20                       ` David Edelsohn
2017-12-18 19:21                         ` Andreas Arnez
2017-12-15 14:49       ` Sergio Durigan Junior
2017-12-15 21:19       ` Yao Qi
2017-12-15 22:40         ` David Edelsohn
2017-12-15 23:19           ` Sergio Durigan Junior
2017-12-19 10:12             ` Joel Brobecker
2017-12-19 11:15           ` Yao Qi
2018-01-15 22:29 ` [BuildBot] Notifications re-enabled for the Debian-s390x-* builders (was: Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders) Sergio Durigan Junior

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=CAGWvnykwWnHYjhXH08LSgiyvxgEyaMVFp9GU0N+KBDsbgrbmwA@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=emachado@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=sergiodj@redhat.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