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: Thu, 30 Jun 2022 14:55:02 +0200	[thread overview]
Message-ID: <580fd1bf36aa2cd76f5f8d7c280f11244cedc382.camel@klomp.org> (raw)
In-Reply-To: <20220630125023.8C6A73842AD9@sourceware.org>

On Thu, 2022-06-30 at 12:50 +0000, builder--- via Dwz wrote:
> A restored build has been detected on builder dwz-rawhide-x86_64
> while building dwz.

Cool, it works! The rawhide build was indeed broken and got fixed when
the alt file workaround fix was checked in. Now the only red dwz
builder is dwz-opensusetw-x86_64:
https://builder.sourceware.org/buildbot/#/builders?tags=dwz

  reply	other threads:[~2022-06-30 12:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 12:50 builder
2022-06-30 12:55 ` Mark Wielaard [this message]
  -- 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-25 21:56 builder
2022-06-25 22:17 ` Mark Wielaard
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
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=580fd1bf36aa2cd76f5f8d7c280f11244cedc382.camel@klomp.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).