public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Date: Wed, 02 Nov 2022 15:19:17 +0100	[thread overview]
Message-ID: <2795ea045a9fcc90220d2164c551c607eed15fef.camel@klomp.org> (raw)
In-Reply-To: <20221102133920.439BB3858C50@sourceware.org>

Hi,

On Wed, 2022-11-02 at 13:39 +0000, builder--- via Elfutils-devel wrote:
> A new failure has been detected on builder elfutils-centos-x86_64
> while building elfutils.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/39/builds/99
> 
> Build state: failed test (failure)
> Revision: e9f3045caa5c4498f371383e5519151942d48b6d
> Worker: centos-x86_64
> Build Reason: (unknown)
> Blamelist: Mark Wielaard <mark@klomp.org>
> 
> Steps:
> [...]
> https://builder.sourceware.org/buildbot/#builders/39/builds/99/steps/6/logs/warnings__2_
> 
> - 7: make check ( failure )
>     Logs:
>         - stdio: 
> https://builder.sourceware.org/buildbot/#builders/39/builds/99/steps/7/logs/stdio
>         - test-suite.log: 
> https://builder.sourceware.org/buildbot/#builders/39/builds/99/steps/7/logs/test-suite_log

So this is run-backtrace-native-core-biarch.sh which only occasionally
fails. It also fails on on debian-testing. It looks like the pc is off
when the core file is generated, which might be a kernel issue, but I
don't understand why it only happens sometimes. Might be because there
are two threads running?

It seems we have two tests that occasionally fail. Which is not good.
But also not that bad that it should stop the release imho.

Cheers,

Mark

  reply	other threads:[~2022-11-02 14:19 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 13:39 builder
2022-11-02 14:19 ` Mark Wielaard [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  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 13:19 builder
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=2795ea045a9fcc90220d2164c551c607eed15fef.camel@klomp.org \
    --to=mark@klomp.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).