public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: dwz@sourceware.org
Subject: Re: ☺ Buildbot (GNU Toolchain): dwz - build successful (master)
Date: Sun, 26 Jun 2022 00:17:36 +0200	[thread overview]
Message-ID: <YreJgCAVrGF3/G3M@wildebeest.org> (raw)
In-Reply-To: <20220625215613.349A43851AA8@sourceware.org>

Hi,

On Sat, Jun 25, 2022 at 09:56:13PM +0000, builder--- via Dwz wrote:
> A restored build has been detected on builder dwz-opensuseleap-x86_64 while building dwz.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/99/builds/2
> 
> Build state: build successful
> Revision: b31d0ebd259a7037e43720cc9599ba37a283a698
> Worker: bb1
> Build Reason: (unknown)
> Blamelist: Lv Ying via Dwz <dwz@sourceware.org>

The previous failure wasn't caused by the above patch, but because
eu-strip was missing on the builder. That has been fixed:
https://sourceware.org/pipermail/buildbot/2022q2/000088.html

The build is now green on all builders except one:
https://builder.sourceware.org/buildbot/#/builders?tags=dwz
dwz-opensusetw-x86_64 fails one testcase: odr-struct-ns.sh
https://builder.sourceware.org/buildbot/#/builders/100/builds/2

Martin, could you take a look at what is different on tumbleweed from
the other builders that makes that testcase fail?

Thanks,

Mark


  reply	other threads:[~2022-06-25 22:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25 21:56 builder
2022-06-25 22:17 ` Mark Wielaard [this message]
2022-06-27  7:25   ` Martin Liška
2022-06-28 21:43     ` Mark Wielaard
2022-06-29  7:17       ` Florian Weimer
2022-06-30 14:23       ` Martin Liška
2022-06-30 20:05         ` Mark Wielaard
2022-07-01  6:42           ` Martin Liška
2022-07-01  7:43             ` Mark Wielaard
2022-07-01  7:53               ` Martin Liška
  -- strict thread matches above, loose matches on Subject: below --
2022-11-03 22:18 builder
2022-07-11  8:44 builder
2022-07-11  8:44 builder
2022-07-07 15:29 builder
2022-07-07 13:12 builder
2022-07-07 13:10 builder
2022-07-07 12:46 builder
2022-07-07 12:46 builder
2022-07-07 12:39 builder
2022-07-07 12:38 builder
2022-07-07 12:32 builder
2022-07-07 12:31 builder
2022-07-01  7:56 builder
2022-06-30 12:50 builder
2022-06-30 12:55 ` Mark Wielaard
2022-06-25 21:55 builder

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=YreJgCAVrGF3/G3M@wildebeest.org \
    --to=mark@klomp.org \
    --cc=dwz@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).