public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Aaron Merey <amerey@redhat.com>
To: elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)
Date: Wed, 1 Nov 2023 23:22:17 -0400	[thread overview]
Message-ID: <CAJDtP-RyLUyXmbSG4qVye-pyJVxWKAcCSc4synHT8f59vQbMGg@mail.gmail.com> (raw)
In-Reply-To: <20231102013555.2DA3D3858D32@sourceware.org>

This fedora-s390x buildbot failure is probably spurious.

The testsuite passed on the s390x trybot.  I also ran the testsuite
on a different F38 s390x machine and again it passed.

Aaron

On Wed, Nov 1, 2023 at 9:36 PM <builder@sourceware.org> wrote:
>
> A new failure has been detected on builder elfutils-fedora-s390x while building elfutils.
>
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/43/builds/240
>
> Build state: failed test (failure)
> Revision: a34c5faad861efdd26d1c52b4f8d9d4077e03131
> Worker: fedora-s390x
> Build Reason: (unknown)
> Blamelist: Aaron Merey <amerey@redhat.com>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: set package name ( success )
>
> - 2: git checkout ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/2/logs/stdio
>
> - 3: autoreconf ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/3/logs/stdio
>
> - 4: configure ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/4/logs/stdio
>         - config.log: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/4/logs/config_log
>
> - 5: get version ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/5/logs/stdio
>         - property changes: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/5/logs/property_changes
>
> - 6: make ( warnings )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/6/logs/stdio
>         - warnings (3): https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/6/logs/warnings__3_
>
> - 7: make check ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/7/logs/stdio
>         - test-suite.log: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/7/logs/test-suite_log
>
> - 8: prep ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/8/logs/stdio
>
> - 9: build bunsen.cpio.gz ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/9/logs/stdio
>
> - 10: fetch bunsen.cpio.gz ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/10/logs/stdio
>
> - 11: unpack bunsen.cpio.gz ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/11/logs/stdio
>
> - 12: pass .bunsen.source.gitname ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/12/logs/stdio
>
> - 13: pass .bunsen.source.gitdescribe ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/13/logs/stdio
>
> - 14: pass .bunsen.source.gitbranch ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/14/logs/stdio
>
> - 15: pass .bunsen.source.gitrepo ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/15/logs/stdio
>
> - 16: upload to bunsen ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/16/logs/stdio
>
> - 17: clean up ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/17/logs/stdio
>
> - 18: make distclean ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/240/steps/18/logs/stdio
>


  reply	other threads:[~2023-11-02  3:22 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  1:35 builder
2023-11-02  3:22 ` Aaron Merey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-02 22:34 builder
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-05-08 16:30 builder
2023-05-08 16:45 ` 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=CAJDtP-RyLUyXmbSG4qVye-pyJVxWKAcCSc4synHT8f59vQbMGg@mail.gmail.com \
    --to=amerey@redhat.com \
    --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).