From: Simon Marchi <simark@simark.ca>
To: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org,
Tom Tromey <tom@tromey.com>
Subject: Re: Breakage on builder Fedora-x86_64-native-gdbserver-m64, revision bfa2a36d94d124eb7b54fd271a543047579b47ee
Date: Mon, 22 Jul 2019 17:28:00 -0000 [thread overview]
Message-ID: <42ec8010-ab5a-96a7-a8c4-72f159c2c5ea@simark.ca> (raw)
In-Reply-To: <E1hpai3-0008Nr-SI@gdb-buildbot.osci.io>
On 2019-07-22 11:58 a.m., gdb-buildbot@sergiodj.net wrote:
> command timed out: 1200 seconds without output running [b'make', b'-j4', b'all'], attempting to kill
> process killed by signal 9
> program finished with exit code -1
> elapsedTime=2105.914565
I talked to Sergio on IRC about these failures, he said there were other jobs on
the machine consuming too much resources. He reduced them, so the GDB jobs should
go back to normal.
Simon
prev parent reply other threads:[~2019-07-22 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 15:58 Oh dear. I regret to inform you that commit bfa2a36d94d124eb7b54fd271a543047579b47ee might be unfortunate gdb-buildbot
2019-07-22 15:58 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, revision bfa2a36d94d124eb7b54fd271a543047579b47ee gdb-buildbot
2019-07-22 17:28 ` Simon Marchi [this message]
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=42ec8010-ab5a-96a7-a8c4-72f159c2c5ea@simark.ca \
--to=simark@simark.ca \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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