From: Pedro Alves <palves@redhat.com>
To: David Edelsohn <dje.gcc@gmail.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 16:20:00 -0000 [thread overview]
Message-ID: <e6fe9ffb-f590-1fef-1e7c-93502c1d3a1a@redhat.com> (raw)
In-Reply-To: <CAGWvnykwWnHYjhXH08LSgiyvxgEyaMVFp9GU0N+KBDsbgrbmwA@mail.gmail.com>
On 12/15/2017 03:53 PM, David Edelsohn wrote:
> 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.
Those are separate machines. I'd like to see the jump on the same
machine, so we can maybe pinpoint what caused it.
I was really asking for URLs. Here looks like there's some:
https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64
Here, for example:
https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/4351
"test gdb tested GDB failed (9 hrs, 2 mins, 56 secs)"
That's definitely too long.
I downloaded the gdb.log file, and did:
$ grep FAIL gdb.log | grep timeout | sed 's/.exp.*/.exp/g' | sort | uniq -c | sort -n
1 FAIL: gdb.base/watch-cond.exp
1 FAIL: gdb.multi/watchpoint-multi-exit.exp
1 FAIL: gdb.threads/interrupted-hand-call.exp
1 FAIL: gdb.threads/thread-unwindonsignal.exp
2 FAIL: gdb.base/value-double-free.exp
3 FAIL: gdb.mi/mi-async.exp
3 FAIL: gdb.threads/process-dies-while-detaching.exp
4 FAIL: gdb.base/pr11022.exp
10 FAIL: gdb.base/watch-bitfields.exp
15 FAIL: gdb.base/watchpoints.exp
20 FAIL: gdb.threads/interrupt-while-step-over.exp
32 FAIL: gdb.threads/watchpoint-fork.exp
45 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp
46 FAIL: gdb.base/display.exp
51 FAIL: gdb.base/watchpoint.exp
Not _that_ many. Could they explain the long time? I suspect not.
We see this:
$ grep "Test run by" gdb.log | head -n 3
Test run by dje on Tue Nov 21 03:23:01 2017
Test run by dje on Tue Nov 21 03:23:01 2017
Test run by dje on Tue Nov 21 03:23:01 2017
$ grep "Test run by" gdb.log | tail -n 3
Test run by dje on Tue Nov 21 03:29:54 2017
Test run by dje on Tue Nov 21 03:29:54 2017
Test run by dje on Tue Nov 21 03:29:54 2017
So most of the testsuite actually ran for 7 minutes. And then
something hung for 9 hours? I have no idea how that
could happen from the existing logs. The tail end of the log has:
~~~
FAIL: gdb.base/watchpoint.exp: delete all breakpoints in delete_breakpoints (timeout)
ERROR: breakpoints not deleted
ERROR: breakpoints not deleted
command timed out: 1200 seconds without output running ['make', '-k', 'check', 'RUNTESTFLAGS=--target_board native-gdbserver', '-j8', 'FORCE_PARALLEL=1'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=32576.210392
~~~
I don't understand how 7 minutes plus 1200 seconds (~20min)
resulted in "elapsedTime=32576.210392" (~9h). Maybe that number
isn't to be trusted.
Anyway, I'm sorry, but I really don't have the time to be
looking at this. Someone with the motivation and access to
the machine could try running the testsuite manually,
for example, see how long that takes, and where the hang is.
> 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,
Pedro Alves
next prev parent reply other threads:[~2017-12-15 16:20 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
2017-12-15 16:20 ` Pedro Alves [this message]
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=e6fe9ffb-f590-1fef-1e7c-93502c1d3a1a@redhat.com \
--to=palves@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=emachado@redhat.com \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).