public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Cc: Xi Ruoyao <xry111@xry111.site>
Subject: Re: ☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)
Date: Tue, 29 Aug 2023 16:20:17 +0200	[thread overview]
Message-ID: <6dd3d9702f5f9f67517e0f33baa6567dc7889aa7.camel@klomp.org> (raw)
In-Reply-To: <20230829140404.612E33858C20@sourceware.org>

Hi,

On Tue, 2023-08-29 at 14:04 +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/216
> 
> Build state: failed test (failure)
> Revision: 2ba424d65adca45b799a3973d43ccaf4002cb833
> Worker: centos-x86_64
> Build Reason: (unknown)
> Blamelist: Xi Ruoyao <xry111@xry111.site>

This isn't caused by that commit.

> - 7: make check ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/216/steps/7/logs/stdio
>         - test-suite.log: https://builder.sourceware.org/buildbot/#builders/39/builds/216/steps/7/logs/test-suite_log

Unfortunately this happens occasionally on this centos7 x86_64 setup.
The issue is that only the "child" thread can be unwound, but not the
main thread. I don't know why however, since it doesn't happen always.
It could be that the kernel generates a bad core file or that the main
thread is in a weird state (without unwind cfi) after the clone.

Cheers,

Mark

  reply	other threads:[~2023-08-29 14:20 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 14:04 builder
2023-08-29 14:20 ` 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-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=6dd3d9702f5f9f67517e0f33baa6567dc7889aa7.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=xry111@xry111.site \
    /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).