From: Mark Wielaard <mark@klomp.org>
To: Ben Woodard <woodard@redhat.com>,
"Guillermo E. Martinez via Libabigail"
<libabigail@sourceware.org>
Subject: Re: ☺ Buildbot (GNU Toolchain): libabigail - build successful (master)
Date: Tue, 03 May 2022 13:11:54 +0200 [thread overview]
Message-ID: <ac067d3eea4e386378c015e4fc5682389ddcee58.camel@klomp.org> (raw)
In-Reply-To: <20220502163012.D05263858C50@sourceware.org>
Hi,
On Mon, 2022-05-02 at 16:30 +0000, builder--- via Libabigail wrote:
> A restored build has been detected on builder libabigail-fedora-ppc64
> while building libabigail.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/51/builds/2
>
> Build state: build successful
> Revision: f52c0ba41654a5ea7baa1be4fdaaefa18a94ae47
> Worker: fedora-ppc64
> Build Reason: (unknown)
> Blamelist: Ben Woodard <woodard@redhat.com>, Guillermo E. Martinez
> via Libabigail <libabigail@sourceware.org>
That is my fault. When I switched over most builders from doing a full
make distcheck to just a make check I missed that the "SLOW" tests were
only done for full distchecks. So now the builder didn't see the
failure on fedora-ppc64 and debian-ppc64 and thinks everything is fine
again.
Frank already fixed it on the builder:
https://sourceware.org/git/?p=builder.git;a=commitdiff;h=0a47ba074f2ad5550bffc2282ae7d86eb5597e9f
This does mean the ppc64 builds will flip from success to failure again
until something like the fix I proposed is integrated:
https://sourceware.org/pipermail/libabigail/2022q2/004318.html
Cheers,
Mark
next prev parent reply other threads:[~2022-05-03 11:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 16:30 builder
2022-05-03 11:11 ` Mark Wielaard [this message]
2022-05-30 9:16 builder
2022-06-09 10:40 builder
2022-06-15 14:04 builder
2022-06-18 20:11 builder
2022-06-23 14:12 builder
2022-07-01 13:16 builder
2022-07-18 22:12 builder
2022-07-19 17:07 builder
2022-07-23 0:12 builder
2022-07-24 16:42 builder
2022-09-05 16:12 builder
2022-09-13 9:45 builder
2022-09-20 8:07 builder
2022-09-26 6:58 builder
2022-10-10 12:19 builder
2022-11-30 16:58 builder
2022-12-19 17:49 builder
2022-12-19 17:49 builder
2022-12-19 18:19 builder
2023-01-06 21:23 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=ac067d3eea4e386378c015e4fc5682389ddcee58.camel@klomp.org \
--to=mark@klomp.org \
--cc=libabigail@sourceware.org \
--cc=woodard@redhat.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).