public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org, Sam James <sam@gentoo.org>,
	 buildbot@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) (master)
Date: Thu, 19 Oct 2023 13:23:11 +0200	[thread overview]
Message-ID: <37994c7987bb6fd75ad4ee36a1029d8b05b7d11e.camel@klomp.org> (raw)
In-Reply-To: <15888d31-891a-8c70-26c2-8ff860799d14@suse.com>

[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]

Hi Jan (CC Sam and builbot mailinglist),

On Mon, 2023-10-16 at 08:48 +0200, Jan Beulich wrote:
> On 13.10.2023 02:42, builder@sourceware.org wrote:
> > A new failure has been detected on builder binutils-gentoo-sparc while building binutils-gdb.
> > 
> > Full details are available at:
> >     https://builder.sourceware.org/buildbot/#builders/228/builds/1402
> > 
> > Build state: failed test (failure)
> > Revision: 59fed66dcef07b7b33c72d47b609e05569c62523
> > Worker: gentoo-sparc
> > Build Reason: (unknown)
> 
> Imo the rate of fails (iirc unexplained timeouts) is too high here. May
> I ask that this worker be taken out, until the issue can be sorted?

I have applied the attached patch which keeps the binutils sparc
builder, but changes the tag from binutils to binutils-build. This
makes it so that it won't be part of the binutils CI reports (so no
more email notifications), but still runs the build which will show up
on https://builder.sourceware.org/buildbot/ and get the results into
bunsen.

I did the same for the binutils-try-gentoo-sparc builder (changing the
tag from binutils-try to binutils-try-build). So for try builds you
won't get emails about the sparc builder anymore, but the results will
show up on the builder website and in bunsen.

Sam, could you please let us know when the sparc builder is a little
bit more robust so we can reactivate the email notifications again?

Thanks,

Mark

[-- Attachment #2: 0001-Change-tags-on-binutils-gentoo-sparc-builders-to-bin.patch --]
[-- Type: text/x-patch, Size: 1343 bytes --]

From b9ca59001326dfd452900e9319e432c92958a6c9 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Thu, 19 Oct 2023 13:20:52 +0200
Subject: [PATCH] Change tags on  binutils-gentoo-sparc builders to
 binutils[-try]-build

This will make sure the builds are still running, but won't be
included in the (email) reports.

Signed-off-by: Mark Wielaard <mark@klomp.org>
---
 builder/master.cfg | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/builder/master.cfg b/builder/master.cfg
index 89ce04a..0c5ce5b 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -2641,14 +2641,14 @@ c['builders'].append(binutils_try_fedora_arm64_builder)
 binutils_gentoo_sparc_builder = util.BuilderConfig(
 	name="binutils-gentoo-sparc",
         workernames=sparc_workers,
-        tags=["binutils", "gentoo", "sparc"],
+        tags=["binutils-build", "gentoo", "sparc"],
         factory=binutils_factory_libctf)
 c['builders'].append(binutils_gentoo_sparc_builder)
 
 binutils_try_gentoo_sparc_builder = util.BuilderConfig(
 	name="binutils-try-gentoo-sparc",
         workernames=sparc_workers,
-        tags=["binutils-try", "gentoo", "sparc"],
+        tags=["binutils-try-build", "gentoo", "sparc"],
         factory=binutils_factory_libctf)
 c['builders'].append(binutils_try_gentoo_sparc_builder)
 
-- 
2.41.0


       reply	other threads:[~2023-10-19 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231013004211.102B03858436@sourceware.org>
     [not found] ` <15888d31-891a-8c70-26c2-8ff860799d14@suse.com>
2023-10-19 11:23   ` Mark Wielaard [this message]
2023-10-19 11:48     ` Jan Beulich

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=37994c7987bb6fd75ad4ee36a1029d8b05b7d11e.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=buildbot@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=sam@gentoo.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).