From: Sergio Durigan Junior <sergiodj@redhat.com>
To: gdb-patches@sourceware.org, Tom de Vries <tdevries@suse.de>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: Oh dear. I regret to inform you that commit 164e3873cf41d01a9a67396575dceef7489cee64 might be unfortunate
Date: Mon, 24 Jun 2019 19:46:00 -0000 [thread overview]
Message-ID: <87r27iu5pf.fsf@redhat.com> (raw)
In-Reply-To: <164e3873cf41d01a9a67396575dceef7489cee64-master-breakage@gdb-build> (gdb-buildbot@sergiodj.net's message of "Mon, 24 Jun 2019 12:35:13 -0400")
On Monday, June 24 2019, gdb-buildbot@sergiodj.net wrote:
> My lords, ladies, gentlemen, members of the public.
>
> It is a matter of great regret and sadness to inform you that commit:
>
> [gdb/testsuite] Fix label reference in implptr-64bit.exp
> 164e3873cf41d01a9a67396575dceef7489cee64
This was apparently a failure in the worker itself:
https://gdb-buildbot.osci.io/#/builders/14/builds/7/steps/5/logs/stdio
/usr/gnu/bin/as: out of memory allocating 4064 bytes after a total of 3735552 bytes
gmake[2]: *** [Makefile:1632: block.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
gmake[2]: Leaving directory '/opt/gdb-buildbot/home/solaris11-amd64/solaris11-amd64-m64/build/gdb'
gmake[1]: *** [Makefile:9229: all-gdb] Error 2
gmake[1]: Leaving directory '/opt/gdb-buildbot/home/solaris11-amd64/solaris11-amd64-m64/build'
gmake: *** [Makefile:851: all] Error 2
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-06-24 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 16:35 gdb-buildbot
2019-06-24 19:46 ` Sergio Durigan Junior [this message]
2019-06-24 19:57 ` Rainer Orth
2019-06-27 17:47 ` 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=87r27iu5pf.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=tdevries@suse.de \
/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