From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, Tom de Vries <tdevries@suse.de>
Subject: Re: Oh dear. I regret to inform you that commit 164e3873cf41d01a9a67396575dceef7489cee64 might be unfortunate
Date: Mon, 24 Jun 2019 19:57:00 -0000 [thread overview]
Message-ID: <ydd7e9a4uzq.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87r27iu5pf.fsf@redhat.com> (Sergio Durigan Junior's message of "Mon, 24 Jun 2019 15:46:36 -0400")
Hi Sergio,
> 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
indeed: that kernel zone (and its sparcv9 sibling) recently started
running an LLVM buildbot, too, and ran out of swap. Should be better
now, otherwise I'll have to reduce the parallelism of those bots.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2019-06-24 19:57 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
2019-06-24 19:57 ` Rainer Orth [this message]
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=ydd7e9a4uzq.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--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