From: Mark Wielaard <mark@klomp.org>
To: binutils@sourceware.org
Subject: Re: ☺ Buildbot (GNU Toolchain): binutils-gdb - build successful (master)
Date: Thu, 09 Jun 2022 15:18:24 +0200 [thread overview]
Message-ID: <021d0bbd00e6391bd4b7c5757dac44ff19a48927.camel@klomp.org> (raw)
In-Reply-To: <20220609034827.7AECB38582A5@sourceware.org>
Hi,
On Thu, 2022-06-09 at 03:48 +0000, builder--- via Binutils wrote:
> A restored build has been detected on builder binutils-debian-amd64
> while building binutils-gdb.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/68/builds/189
This is because the builder was upgraded from Debian old-stable, 10
(buster) to stable, 11 (bullseye). old-stable had various failures in
the ld testsuite. Those are gone now and all tests (binutils, gas, ld)
now PASS.
Cheers,
Mark
next prev parent reply other threads:[~2022-06-09 13:18 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 3:48 builder
2022-06-09 13:18 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 11:00 builder
2023-01-05 8:52 builder
2022-12-25 8:37 builder
2022-12-17 1:20 builder
2022-12-16 16:03 builder
2022-12-12 18:13 builder
2022-12-12 13:11 builder
2022-12-12 9:14 builder
2022-12-12 8:06 builder
2022-12-07 6:17 builder
2022-11-30 16:44 builder
2022-11-30 16:34 builder
2022-11-30 8:59 builder
2022-11-28 10:22 builder
2022-11-28 3:03 builder
2022-11-21 17:07 builder
2022-11-16 1:51 builder
2022-11-11 7:55 builder
2022-11-07 5:16 builder
2022-11-02 3:13 builder
2022-11-01 11:05 builder
2022-10-31 16:30 builder
2022-10-24 8:00 builder
2022-10-20 0:15 builder
2022-10-19 12:57 builder
2022-10-19 11:47 builder
2022-10-11 13:48 builder
2022-10-06 4:41 builder
2022-10-06 4:00 builder
2022-10-05 7:34 builder
2022-10-05 4:41 builder
2022-10-04 13:52 builder
2022-10-04 8:25 builder
2022-10-03 12:21 builder
2022-09-30 4:24 builder
2022-09-29 0:23 builder
2022-09-28 12:14 builder
2022-09-28 4:48 builder
2022-09-27 5:53 builder
2022-09-27 4:02 builder
2022-09-27 0:18 builder
2022-09-26 15:44 builder
2022-09-26 10:14 builder
2022-09-26 6:03 builder
2022-09-24 2:26 builder
2022-09-22 17:50 builder
2022-09-22 17:30 builder
2022-09-22 7:32 builder
2022-09-20 11:21 builder
2022-09-14 6:00 builder
2022-09-14 0:18 builder
2022-09-08 12:05 builder
2022-09-06 16:03 builder
2022-09-06 2:46 builder
2022-09-02 17:32 builder
2022-09-02 6:42 builder
2022-08-30 15:35 builder
2022-08-28 0:19 builder
2022-08-25 10:55 builder
2022-08-24 16:25 builder
2022-08-23 9:11 builder
2022-08-23 8:53 builder
2022-08-22 9:41 builder
2022-08-20 22:44 builder
2022-08-16 8:02 builder
2022-08-16 7:36 builder
2022-08-14 0:15 builder
2022-08-11 9:34 builder
2022-08-09 8:00 builder
2022-08-06 10:06 builder
2022-08-05 11:48 builder
2022-08-01 4:59 builder
2022-07-26 13:26 builder
2022-07-26 13:06 builder
2022-07-21 22:45 builder
2022-07-19 16:01 builder
2022-07-19 2:09 builder
2022-07-17 0:13 builder
2022-07-08 11:54 builder
2022-07-04 11:41 builder
2022-07-03 16:50 builder
2022-07-03 16:45 builder
2022-06-29 17:01 builder
2022-06-28 1:46 builder
2022-06-27 13:52 builder
2022-06-27 3:18 builder
2022-06-25 0:19 builder
2022-06-21 19:22 builder
2022-06-13 9:36 builder
2022-06-09 4:02 builder
2022-06-02 11:18 builder
2022-06-02 9:44 builder
2022-05-30 8:02 builder
2022-05-30 7:56 builder
2022-05-25 23:53 builder
2022-05-19 11:11 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=021d0bbd00e6391bd4b7c5757dac44ff19a48927.camel@klomp.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
/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).