public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Date: Sat, 23 Apr 2022 09:19:18 -0400	[thread overview]
Message-ID: <E1niFfS-00BGrq-1Y@very.elastic.org> (raw)

A new failure has been detected on builder elfutils-fedora-x86_64 while building elfutils.

Full details are available at:
    http://localhost:8010/#builders/30/builds/28

Build state: failed test (failure)
Revision: 40508c282202b5ff85201d79dc8d32298bb27299
Worker: fedora-x86_64
Build Reason: (unknown)
Blamelist: Frank Ch. Eigler <fche@redhat.com>

Steps:

- 0: worker_preparation ( success )

- 1: set package name ( success )

- 2: git checkout ( success )
    Logs:
        - stdio: http://localhost:8010/#builders/30/builds/28/steps/2/logs/stdio

- 3: autoreconf ( success )
    Logs:
        - stdio: http://localhost:8010/#builders/30/builds/28/steps/3/logs/stdio

- 4: configure ( success )
    Logs:
        - stdio: http://localhost:8010/#builders/30/builds/28/steps/4/logs/stdio

- 5: get version ( success )
    Logs:
        - stdio: http://localhost:8010/#builders/30/builds/28/steps/5/logs/stdio
        - property changes: http://localhost:8010/#builders/30/builds/28/steps/5/logs/property_changes

- 6: make ( warnings )
    Logs:
        - stdio: http://localhost:8010/#builders/30/builds/28/steps/6/logs/stdio
        - warnings (3): http://localhost:8010/#builders/30/builds/28/steps/6/logs/warnings__3_

- 7: make check ( success )
    Logs:
        - stdio: http://localhost:8010/#builders/30/builds/28/steps/7/logs/stdio
        - test-suite.log: http://localhost:8010/#builders/30/builds/28/steps/7/logs/test-suite_log

- 8: make distcheck ( failure )
    Logs:
        - stdio: http://localhost:8010/#builders/30/builds/28/steps/8/logs/stdio
        - test-suite.log: http://localhost:8010/#builders/30/builds/28/steps/8/logs/test-suite_log
        - warnings (4): http://localhost:8010/#builders/30/builds/28/steps/8/logs/warnings__4_


             reply	other threads:[~2022-04-23 13:19 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 13:19 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-14  2:51 builder
2022-12-21 18:22 builder
2022-12-19 23:56 builder
2022-12-12 14:31 builder
2022-11-28 13:30 builder
2022-11-04 22:29 builder
2022-11-03 15:27 builder
2022-11-02 13:39 builder
2022-11-02 14:19 ` Mark Wielaard
2022-11-02  1:15 builder
2022-11-02 12:06 ` Mark Wielaard
2022-11-01 21:28 builder
2022-10-31 13:51 builder
2022-10-27 19:25 builder
2022-10-17 14:59 builder
2022-10-17  9:08 builder
2022-10-17 10:26 ` Mark Wielaard
2022-10-17 11:02   ` Frank Ch. Eigler
2022-10-17 14:09     ` Frank Ch. Eigler
2022-10-16 21:02 builder
2022-10-16 15:47 builder
2022-10-16 16:26 ` Mark Wielaard
2022-10-13 16:51 builder
2022-09-14 19:36 builder
2022-07-31 23:54 builder
2022-08-01  0:09 ` Mark Wielaard
2022-08-01  9:13   ` Mark Wielaard
2022-05-28  9:15 builder
2022-05-28  9:35 ` Mark Wielaard
2022-05-28  9:43   ` Mark Wielaard
2022-06-02 15:44     ` Mark Wielaard
2022-05-27 16:02 builder
2022-05-27 22:30 ` Mark Wielaard
2022-05-28  2:34   ` Frank Ch. Eigler
2022-05-28  9:04     ` Mark Wielaard
2022-05-14 15:34 builder
2022-05-14 16:40 ` Mark Wielaard
2022-05-14 14:42 builder
2022-05-04 15:34 builder
2022-05-04 17:44 ` Mark Wielaard
2022-04-23  1:19 builder
2022-04-23  1:31 ` Mark Wielaard
2022-04-19  9:05 builder
2022-04-19  9:28 ` Mark Wielaard

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=E1niFfS-00BGrq-1Y@very.elastic.org \
    --to=builder@sourceware.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=fche@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).