public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: John Gallagher <john@gllghr.com>, elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)
Date: Mon, 08 May 2023 18:45:25 +0200	[thread overview]
Message-ID: <2a73ec4caeeaa19d751a3e5ce501f03de7286a34.camel@klomp.org> (raw)
In-Reply-To: <20230508163033.E879D3858D35@sourceware.org>

Hi,

On Mon, 2023-05-08 at 16:30 +0000, builder--- via Elfutils-devel wrote:
> A new failure has been detected on builder elfutils-opensusetw-x86_64
> while building elfutils.
>
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/88/builds/157
>
> Build state: failed test (failure)
> Revision: fa7da8bfad1ec2ac61859aa0b4b09b42ea657ea2
> Worker: bb1-2
> Build Reason: (unknown)
> Blamelist: John Gallagher <john@gllghr.com>

> [...]
> - 8: make distcheck ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/88/builds/157/steps/8/logs/stdio
>         - test-suite.log: https://builder.sourceware.org/buildbot/#builders/88/builds/157/steps/8/logs/test-suite_log
>         - warnings (3): https://builder.sourceware.org/buildbot/#builders/88/builds/157/steps/8/logs/warnings__3_
> [...]
> A new failure has been detected on builder elfutils-rawhide-x86_64
> while building elfutils.
>
> Full details are available at:
>    https://builder.sourceware.org/buildbot/#builders/140/builds/149
>
> Build state: failed test (failure)
> Revision: fa7da8bfad1ec2ac61859aa0b4b09b42ea657ea2
> Worker: bb1-1
> Build Reason: (unknown)
> Blamelist: John Gallagher <john@gllghr.com>
> [...]
> - 8: make distcheck ( failure )
>    Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/140/builds/149/steps/8/logs/stdio
>         - test-suite.log: https://builder.sourceware.org/buildbot/#builders/140/builds/149/steps/8/logs/test-suite_log
>         - warnings (4): https://builder.sourceware.org/buildbot/#builders/140/builds/149/steps/8/logs/warnings__4_
> [...]

In both cases it is the run-debuginfod-federation-metrics.sh test
FAILing. Which is sadly known to be buggy. The next build has both
builders green. So it is indeed flaky. Sigh.

Sorry for the noise.

Cheers,

Mar

  reply	other threads:[~2023-05-08 16:45 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 16:30 builder
2023-05-08 16:45 ` Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-02 22:34 builder
2023-11-02  1:35 builder
2023-11-02  3:22 ` Aaron Merey
2023-11-01 15:08 builder
2023-11-01 16:40 ` Mark Wielaard
2023-10-24 20:37 builder
2023-10-14 15:32 builder
2023-10-14 15:44 ` Mark Wielaard
2023-10-03 18:08 builder
2023-10-03 16:50 builder
2023-08-29 14:04 builder
2023-08-29 14:20 ` Mark Wielaard
2023-07-20 11:37 builder
2023-07-20 13:07 ` Mark Wielaard
2023-06-27 14:52 builder
2023-06-17  0:56 builder
2023-06-16 16:16 builder
2023-06-16 16:50 ` Mark Wielaard
2023-05-12 21:04 builder
2023-05-12 21:29 ` Mark Wielaard
2023-05-09 12:05 builder
2023-05-09 12:12 ` Mark Wielaard
2023-05-09 10:20 builder
2023-05-09 10:39 ` Mark Wielaard
2023-04-17 12:36 builder
2023-04-17 12:46 ` Mark Wielaard
2023-04-14 15:49 builder
2023-04-13 18:01 builder
2023-04-06 23:20 builder
2023-04-07 19:33 ` Mark Wielaard
2023-03-30 20:48 builder
2023-03-29 22:28 builder
2023-03-29 22:18 builder
2023-03-05 12:52 builder
2023-02-28 13:12 builder
2023-02-17 20:36 builder
2023-02-17 20:39 ` Mark Wielaard
2023-02-14 17:02 builder
2023-02-14 17:33 ` Mark Wielaard
2023-02-14 16:56 builder
2023-02-14 17:31 ` Mark Wielaard
2023-02-14 16:14 builder
2023-02-14 16:37 ` Mark Wielaard
2023-02-09 14:56 builder
2023-02-09 14:20 builder
2023-02-09 14:30 ` Mark Wielaard
2023-02-08 17:57 builder
2023-02-08 18:26 ` Mark Wielaard
2023-02-08  2:43 builder
2023-02-08  3:29 ` Aaron Merey
2023-02-08 12:23   ` Frank Ch. Eigler

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=2a73ec4caeeaa19d751a3e5ce501f03de7286a34.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=john@gllghr.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).