public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Mark Wielaard <mark@klomp.org>
Cc: gdb-testers@sourceware.org, Tom Tromey <tromey@adacore.com>
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed configure (failure) (master)
Date: Tue, 14 Feb 2023 09:59:51 -0500 [thread overview]
Message-ID: <m3v8k4qom0.fsf@fitzsim.org> (raw)
In-Reply-To: <m3h6vprwc5.fsf@fitzsim.org> (Thomas Fitzsimmons's message of "Mon, 13 Feb 2023 18:15:22 -0500")
Hi,
OK, I helped the usrmerge script get to completion then got everything
updated to Debian sid latest. The reboot worked fine and the builder
started right up. The "gdb-debian-ppc64" is succeeding now. Sorry for
the disruption. Debian on this worker should be easier to upgrade from
now on, post-usrmerge.
Tom
Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:
> Hi Mark,
>
> Thanks for sending. I'm upgrading Debian sid on the builder and it
> looks like the "usrmerge" installation stopped apt. I've disabled the
> builder for now, and will work on getting the system up-to-date before
> re-enabling it.
>
> Tom
>
> Mark Wielaard <mark@klomp.org> writes:
>
>> Hi Tom F,
>>
>> Could you take a look at this odd configure failure on the ppc64 worker?
>> It doesn't look like it is caused by the commit by Tom T.
>>
>> expr: /usr/lib/powerpc64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by expr)
>>
>> That looks like somehow glibc was downgraded? But not coreutils?
>>
>> Thanks,
>>
>> Mark
>>
>> On Mon, Feb 13, 2023 at 10:09:09PM +0000, builder--- via Gdb-testers wrote:
>>> A new failure has been detected on builder gdb-debian-ppc64 while building binutils-gdb.
>>>
>>> Full details are available at:
>>> https://builder.sourceware.org/buildbot/#builders/76/builds/2872
>>>
>>> Build state: failed configure (failure)
>>> Revision: da59d966b8d182653f9bf3cfa93f921e8993757b
>>> Worker: debian-ppc64
>>> Build Reason: (unknown)
>>> Blamelist: Tom Tromey <tromey@adacore.com>
>>>
>>> Steps:
>>>
>>> - 0: worker_preparation ( success )
>>>
>>> - 1: git checkout ( success )
>>> Logs:
>>> - stdio: https://builder.sourceware.org/buildbot/#builders/76/builds/2872/steps/1/logs/stdio
>>>
>>> - 2: rm -rf gdb-build ( success )
>>> Logs:
>>> - stdio: https://builder.sourceware.org/buildbot/#builders/76/builds/2872/steps/2/logs/stdio
>>>
>>> - 3: configure ( failure )
>>> Logs:
>>> - stdio: https://builder.sourceware.org/buildbot/#builders/76/builds/2872/steps/3/logs/stdio
>>> - config.log: https://builder.sourceware.org/buildbot/#builders/76/builds/2872/steps/3/logs/config_log
>>>
next prev parent reply other threads:[~2023-02-14 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 22:09 builder
2023-02-13 22:47 ` Mark Wielaard
2023-02-13 23:15 ` Thomas Fitzsimmons
2023-02-14 14:59 ` Thomas Fitzsimmons [this message]
2024-01-13 1:21 builder
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=m3v8k4qom0.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=gdb-testers@sourceware.org \
--cc=mark@klomp.org \
--cc=tromey@adacore.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).