From: Joel Brobecker <brobecker@adacore.com>
To: gdb-buildbot@sergiodj.net
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, revision 6181e9c2c5ba252ac016f51903dc35d7bfbbca71
Date: Fri, 12 Jan 2018 03:07:00 -0000 [thread overview]
Message-ID: <20180112030705.nl2jkoddefjlpk2p@adacore.com> (raw)
In-Reply-To: <E1eZpFO-0001v4-Qz@kwanyin.sergiodj.net>
> make[4]: fork: Resource temporarily unavailable
Uh oh....
--
Joel
next prev parent reply other threads:[~2018-01-12 3:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 2:39 Oh dear. I regret to inform you that commit 6181e9c2c5ba252ac016f51903dc35d7bfbbca71 might be unfortunate gdb-buildbot
2018-01-12 2:39 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, revision 6181e9c2c5ba252ac016f51903dc35d7bfbbca71 gdb-buildbot
2018-01-12 3:07 ` Joel Brobecker [this message]
2018-01-12 5:52 ` 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=20180112030705.nl2jkoddefjlpk2p@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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