From: Mark Wielaard <mark@klomp.org>
To: builder@sourceware.org
Cc: elfutils-devel@sourceware.org
Subject: Re: ☺ Buildbot (GNU Toolchain): elfutils - build successful (master)
Date: Tue, 03 May 2022 17:02:29 +0200 [thread overview]
Message-ID: <dc68c9e95d9c378632087752c19c7aed6fb9b90a.camel@klomp.org> (raw)
In-Reply-To: <20220503002512.9D7EB3857815@sourceware.org>
Hi,
On Tue, 2022-05-03 at 00:25 +0000, builder--- via Elfutils-devel wrote:
> A restored build has been detected on builder elfutils-fedora-x86_64
> while building elfutils.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/59/builds/14
>
> Build state: build successful
> Revision: 6d0c3b57429add5b6494259c1c06499e52cff4d5
> Worker: fedora-x86_64
> Build Reason: (unknown)
> Blamelist: Mark Wielaard <mark@klomp.org>
This is a little cheating. I removed the --enable-valgrind from make
distcheck and this failed before because of some (valgrind I suspect)
bug that caused a zstd using test to fail. Once we add --enable-
valgrind back for this distro/arch (fedora 35 x86_64) the failure would
come back. But for now we are all green! :)
https://builder.sourceware.org/buildbot/#/builders?tags=elfutils
Cheers,
Mark
next prev parent reply other threads:[~2022-05-03 15:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 0:25 builder
2022-05-03 15:02 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-21 19:24 builder
2022-12-20 18:26 builder
2022-12-13 17:11 builder
2022-12-12 20:57 builder
2022-11-29 10:00 builder
2022-11-21 17:48 builder
2022-11-07 17:55 builder
2022-11-03 15:44 builder
2022-11-03 14:45 builder
2022-11-02 17:32 builder
2022-11-02 0:22 builder
2022-11-01 23:03 builder
2022-10-27 19:50 builder
2022-10-27 14:11 builder
2022-10-16 21:18 builder
2022-10-16 16:58 builder
2022-09-27 16:07 builder
2022-08-07 23:42 builder
2022-08-03 15:18 builder
2022-08-01 10:40 builder
2022-08-01 9:36 builder
2022-08-01 10:22 ` Mark Wielaard
2022-07-29 18:47 builder
2022-07-13 19:05 builder
2022-07-13 19:04 builder
2022-07-13 19:03 builder
2022-07-13 19:00 builder
2022-07-13 18:56 builder
2022-07-13 18:55 builder
2022-07-13 18:53 builder
2022-07-13 18:53 builder
2022-07-13 18:51 builder
2022-07-13 18:50 builder
2022-07-13 18:50 builder
2022-07-13 18:47 builder
2022-07-10 22:52 builder
2022-06-02 17:31 builder
2022-05-27 22:40 builder
2022-05-14 22:37 builder
2022-05-14 15:08 builder
2022-05-10 1:10 builder
2022-04-24 11:05 builder
2022-04-23 1:22 builder
2022-04-19 14:05 builder
2022-04-19 10:20 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=dc68c9e95d9c378632087752c19c7aed6fb9b90a.camel@klomp.org \
--to=mark@klomp.org \
--cc=builder@sourceware.org \
--cc=elfutils-devel@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).