public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org, Omar Sandoval <osandov@fb.com>
Cc: Sam James <sam@gentoo.org>, buildbot@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)
Date: Wed, 01 Nov 2023 17:40:10 +0100	[thread overview]
Message-ID: <6f9f6d29868011a05ce9268dd555f15d4e008d1b.camel@klomp.org> (raw)
In-Reply-To: <20231101150800.B53003858C5E@sourceware.org>

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

Hi,

On Wed, 2023-11-01 at 15:08 +0000, builder@sourceware.org wrote:
> A new failure has been detected on builder elfutils-gentoo-sparc while building elfutils.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/225/builds/115
> 
> Build state: failed test (failure)
> Revision: c112cf0f1975e19a6111f594c0e5c4d2210c0f9a
> Worker: gentoo-sparc
> Build Reason: (unknown)
> Blamelist: Omar Sandoval <osandov@fb.com>
> 
> Steps:
> 
> - 7: make check ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/115/steps/7/logs/stdio
>         - test-suite.log: https://builder.sourceware.org/buildbot/#builders/225/builds/115/steps/7/logs/test-suite_log

   command timed out: 1200 seconds without output running [b'make',
   b'check', b'-j8', b'--output-sync=line'], attempting to kill
   process killed by signal 9
   program finished with exit code -1
   elapsedTime=1289.277272
   
So that is the sparc builder getting stuck again. Not caused by Omar's
patch.

I have applied the attached patch which keeps the elfutils sparc
builder, but changes the tag from elfutils to elfutils-build. This
makes it so that it won't be part of the elfutils 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 elfutils-try-gentoo-sparc builder (changing the
tag from elfutils-try to elfutils-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-elfutils-gentoo-sparc-builders-to-elf.patch --]
[-- Type: text/x-patch, Size: 1341 bytes --]

From 63e9a80421d27f8195b2d96b90af3980c24335ac Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Wed, 1 Nov 2023 17:37:12 +0100
Subject: [PATCH] Change tags on elfutils-gentoo-sparc builders to
 elfutils[-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 ab8b90b..4a40edf 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -2004,14 +2004,14 @@ c['builders'].append(elfutils_try_fedora_arm64_builder)
 elfutils_gentoo_sparc_builder = util.BuilderConfig(
         name="elfutils-gentoo-sparc",
         workernames=sparc_workers,
-        tags=["elfutils", "gentoo", "sparc"],
+        tags=["elfutils-build", "gentoo", "sparc"],
         factory=elfutils_factory)
 c['builders'].append(elfutils_gentoo_sparc_builder)
 
 elfutils_try_gentoo_sparc_builder = util.BuilderConfig(
         name="elfutils-try-gentoo-sparc",
         workernames=sparc_workers,
-        tags=["elfutils-try", "gentoo", "sparc"],
+        tags=["elfutils-try-build", "gentoo", "sparc"],
         factory=elfutils_factory)
 c['builders'].append(elfutils_try_gentoo_sparc_builder)
 
-- 
2.41.0


  reply	other threads:[~2023-11-01 16:40 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 15:08 builder
2023-11-01 16:40 ` 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-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-08-29 14:04 builder
2023-08-29 14:20 ` Mark Wielaard
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=6f9f6d29868011a05ce9268dd555f15d4e008d1b.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=osandov@fb.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).