public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@tarox.wildebeest.org>
To: gdb-testers@sourceware.org
Cc: Jan Beulich <jbeulich@suse.com>, Nick Clifton <nickc@redhat.com>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Wed, 18 May 2022 15:45:26 +0200	[thread overview]
Message-ID: <20220518134526.GA13942@tarox.wildebeest.org> (raw)
In-Reply-To: <20220518130236.543463856274@sourceware.org>

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

Hi,

On Wed, May 18, 2022 at 01:02:36PM +0000, builder@sourceware.org wrote:
> A new failure has been detected on builder gdb-debian-armhf while building binutils-gdb.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/72/builds/210
> 
> Build state: failed test (failure)
> Revision: 4bb8b8e9381bce9734454470ebd1572534e7514e
> Worker: debian-armhf
> Build Reason: (unknown)
> Blamelist: Jan Beulich <jbeulich@suse.com>, Nick Clifton <nickc@redhat.com>
> [...]
> - 5: make check-gdb ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/210/steps/5/logs/stdio
>         - gdb.sum: https://builder.sourceware.org/buildbot/#builders/72/builds/210/steps/5/logs/gdb_sum
>         - gdb.log: https://builder.sourceware.org/buildbot/#builders/72/builds/210/steps/5/logs/gdb_log

Sigh. Sorry about that. Apparently make gdb-check is flaky on debian-armhf.
See also https://sourceware.org/bugzilla/show_bug.cgi?id=28561

I have disabled the gdb-check on armhf for now.

Cheers,

Mark

[-- Attachment #2: 0001-gdb-Disable-make-check-for-gdb-debian-armhf-builder.patch --]
[-- Type: text/plain, Size: 3365 bytes --]

>From b00886897ea3d65410f2fd56aead11104a0b3fb9 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Wed, 18 May 2022 15:40:43 +0200
Subject: [PATCH] gdb: Disable make check for gdb-debian-armhf builder

make gdb-check is flaky on armhf.
Tracked at https://sourceware.org/bugzilla/show_bug.cgi?id=28561
---
 builder/master.cfg | 38 ++++++++++++++++++++++++++------------
 1 file changed, 26 insertions(+), 12 deletions(-)

diff --git a/builder/master.cfg b/builder/master.cfg
index 27b8dc1..06c388f 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -1217,33 +1217,32 @@ c['builders'].append(binutils_fedora_ppc64le_builder)
 
 # gdb build steps, factory and builders
 
-gdb_factory = util.BuildFactory()
-gdb_factory.addStep(steps.Git(
+gdb_git_step = steps.Git(
         workdir='binutils-gdb',
         repourl=binutils_gdb_repourl,
         mode='full', method='fresh',
         name="git checkout",
-        haltOnFailure=True))
-gdb_factory.addStep(steps.ShellCommand(
+        haltOnFailure=True)
+gdb_rm_step = steps.ShellCommand(
         command=["rm", "-rf",
                  util.Interpolate ("%(prop:builddir)s/gdb-build")],
         name="rm -rf gdb-build",
-        haltOnFailure=True))
-gdb_factory.addStep(steps.Configure(
+        haltOnFailure=True)
+gdb_configure_step = steps.Configure(
         workdir='gdb-build',
         command=['../binutils-gdb/configure',
                  '--enable-target=all'],
         name='configure',
-        haltOnFailure=True))
-gdb_factory.addStep(steps.Compile(
+        haltOnFailure=True)
+gdb_make_step = steps.Compile(
         workdir='gdb-build',
         command=['make',
                  util.Interpolate('-j%(prop:ncpus)s'),
                  'all-gdb', 'all-gdbserver'],
         name='make',
-        haltOnFailure=True))
+        haltOnFailure=True)
 # Only a small subset of tests that are fast and known to PASS.
-gdb_factory.addStep(steps.Test(
+gdb_check_step = steps.Test(
         workdir='gdb-build',
         command=['make',
                  util.Interpolate('-j%(prop:ncpus)s'),
@@ -1255,7 +1254,22 @@ gdb_factory.addStep(steps.Test(
         name='make check-gdb',
         logfiles={ "gdb.sum": "gdb/testsuite/gdb.sum",
                    "gdb.log": "gdb/testsuite/gdb.log" },
-        haltOnFailure=True))
+        haltOnFailure=True)
+
+gdb_factory = util.BuildFactory()
+gdb_factory.addStep(gdb_git_step)
+gdb_factory.addStep(gdb_rm_step)
+gdb_factory.addStep(gdb_configure_step)
+gdb_factory.addStep(gdb_make_step)
+gdb_factory.addStep(gdb_check_step)
+
+# Used for armhf only because of
+# https://sourceware.org/bugzilla/show_bug.cgi?id=28561
+gdb_factory_make_only = util.BuildFactory()
+gdb_factory_make_only.addStep(gdb_git_step)
+gdb_factory_make_only.addStep(gdb_rm_step)
+gdb_factory_make_only.addStep(gdb_configure_step)
+gdb_factory_make_only.addStep(gdb_make_step)
 # NB: no need to BUNSEN ME, test suites are not actually being run
 
 gdb_centos_x86_64_builder = util.BuilderConfig(
@@ -1276,7 +1290,7 @@ gdb_debian_armhf_builder = util.BuilderConfig(
 	name="gdb-debian-armhf",
         workernames=["debian-armhf"],
         tags=["gdb", "debian", "armhf"],
-        factory=gdb_factory)
+        factory=gdb_factory_make_only)
 c['builders'].append(gdb_debian_armhf_builder)
 
 gdb_debian_arm64_builder = util.BuilderConfig(
-- 
2.18.4


  reply	other threads:[~2022-05-18 13:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 13:02 builder
2022-05-18 13:45 ` Mark Wielaard [this message]
2022-05-18 16:30   ` Luis Machado
  -- strict thread matches above, loose matches on Subject: below --
2023-01-11  1:01 builder
2022-12-22  4:09 builder
2022-12-15  0:31 builder
2022-12-06 15:13 builder
2022-11-28 16:22 builder
2022-11-28 16:18 builder
2022-11-22  0:29 builder
2022-11-11 15:20 builder
2022-11-07 16:53 builder
2022-10-26 12:16 builder
2022-10-26  7:45 builder
2022-10-18 15:33 builder
2022-10-16 19:01 builder
2022-10-16 18:51 builder
2022-10-16 17:51 builder
2022-10-16 17:23 builder
2022-10-16 17:23 builder
2022-10-16 17:19 builder
2022-10-16 17:15 builder
2022-10-16 17:05 builder
2022-09-13 12:20 builder
2022-09-12  8:31 builder
2022-08-31 18:22 builder
2022-08-31 17:30 builder
2022-08-03 20:03 builder
2022-07-30  0:27 builder
2022-07-29  7:49 builder
2022-07-19 14:54 builder
2022-07-15 17:52 builder
2022-07-15  0:19 builder
2022-07-08 14:07 builder
2022-06-07 18:34 builder
2022-05-31 15:39 builder
2022-05-18  0:23 builder
2022-05-17 10:50 builder
2022-05-17  5:52 builder
2022-05-15  0:25 builder
2022-05-13 20:18 builder
2022-05-15 15:04 ` Mark Wielaard
2022-05-16  8:25   ` Luis Machado
2022-05-16  8:44     ` Mark Wielaard
2022-05-16  9:12       ` Luis Machado

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=20220518134526.GA13942@tarox.wildebeest.org \
    --to=mark@tarox.wildebeest.org \
    --cc=gdb-testers@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=nickc@redhat.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).