public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Ryan Goldberg <rgoldber@redhat.com>, elfutils-devel@sourceware.org
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>
Subject: Re: ☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)
Date: Fri, 16 Jun 2023 18:50:08 +0200	[thread overview]
Message-ID: <8e1dcc74187c46bc9fbad988b4f67ade0deaf872.camel@klomp.org> (raw)
In-Reply-To: <20230616161601.580E53858D3C@sourceware.org>

Hi Ryan (CC Andreas the s390x valgrind maintainer)

On Fri, 2023-06-16 at 16:16 +0000, builder--- via Elfutils-devel 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/196
> 
> Build state: failed test (failure)
> Revision: 938a52c22ee915ff2cea813edd5da66bc8184885
> Worker: fedora-s390x
> Build Reason: (unknown)
> Blamelist: Ryan Goldberg <rgoldber@redhat.com>

This isn't your fault, or that of the commit.

Valgrind on the s390x testing machine got upgraded (and so did gcc).
The testsuite is run under valgrind, and for some of the tests we get:

vex: priv/guest_s390_toIR.c:16378 (s390_irgen_VGM): Assertion `from <=
to' failed.
vex storage: T total 198202912 bytes allocated
vex storage: P total 0 bytes allocated

valgrind: the 'impossible' happened:
LibVEX called failure_exit().

This seems to be the following valgrind bug:
https://bugs.kde.org/show_bug.cgi?id=470132

Luckily Andreas already suggested a patch for that.

I'll try to apply that patch, install a patched valgrind on the s390x
tester and rerun the elfutils buildbot.

Thanks for providing a testcase for valgrind on s390x :)

Cheers,

Mark

  reply	other threads:[~2023-06-16 16:50 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 16:16 builder
2023-06-16 16:50 ` 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-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=8e1dcc74187c46bc9fbad988b4f67ade0deaf872.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=rgoldber@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).