public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: gdb-testers@sourceware.org
Cc: "Andrew Burgess" <aburgess@redhat.com>,
	"Nick Clifton" <nickc@redhat.com>,
	liuzhensong <liuzhensong@loongson.cn>,
	"Simon Marchi" <simon.marchi@efficios.com>,
	"Simon Marchi" <simon.marchi@polymtl.ca>,
	"Tom de Vries" <tdevries@suse.de>,
	"Bruno Larsen" <blarsen@redhat.com>,
	"John Baldwin" <jhb@freebsd.org>, "Enze Li" <enze.li@hotmail.com>,
	"Keith Seitz" <keiths@redhat.com>,
	"Tsukasa OI" <research_trasio@irq.a4lg.com>,
	"Nelson Chu" <nelson@rivosinc.com>, Shihua <shihua@iscas.ac.cn>,
	"Christoph Müllner" <christoph.muellner@vrull.eu>,
	"Palmer Dabbelt" <palmer@rivosinc.com>,
	"Tom Tromey" <tom@tromey.com>,
	"Luis Machado" <luis.machado@arm.com>,
	"Alan Modra" <amodra@gmail.com>,
	"Fangrui Song" <maskray@google.com>
Subject: Old Buildbot binutils-gdb fail emails
Date: Sun, 16 Oct 2022 21:27:51 +0200	[thread overview]
Message-ID: <Y0xbN8xFTWOMnfjG@wildebeest.org> (raw)
In-Reply-To: <20221016170505.5A1903858C83@sourceware.org>

Apologies,

You might have gotten one or more buildbot failure emails for
binutils-gdb.  These were for old gdb builds. All gdb builders (except
for centos7) are currently green. So no action is required.

This was caused by the disabling of the ibm-power8 worker. This
triggered the sending of old emails for builds the gdb-ibm-power8
builder had skipped.

The good news is that the spurious "failed update" issue has been
fixed. So you shouldn't get emails anymore about bad git updates.

Again sorry for those old emails. 

Cheers,

Mark

      reply	other threads:[~2022-10-16 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 17:05 ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master) builder
2022-10-16 19:27 ` Mark Wielaard [this message]

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=Y0xbN8xFTWOMnfjG@wildebeest.org \
    --to=mark@klomp.org \
    --cc=aburgess@redhat.com \
    --cc=amodra@gmail.com \
    --cc=blarsen@redhat.com \
    --cc=christoph.muellner@vrull.eu \
    --cc=enze.li@hotmail.com \
    --cc=gdb-testers@sourceware.org \
    --cc=jhb@freebsd.org \
    --cc=keiths@redhat.com \
    --cc=liuzhensong@loongson.cn \
    --cc=luis.machado@arm.com \
    --cc=maskray@google.com \
    --cc=nelson@rivosinc.com \
    --cc=nickc@redhat.com \
    --cc=palmer@rivosinc.com \
    --cc=research_trasio@irq.a4lg.com \
    --cc=shihua@iscas.ac.cn \
    --cc=simon.marchi@efficios.com \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.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).