public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: builder@sourceware.org
Cc: Binutils <binutils@sourceware.org>
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) (master)
Date: Thu, 14 Sep 2023 10:58:56 +0200	[thread overview]
Message-ID: <a9f74fed-ac22-c5be-9aad-0118a856b681@suse.com> (raw)
In-Reply-To: <20230914084342.10CE138555A9@sourceware.org>

On 14.09.2023 10:43, 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/1276
> 
> Build state: failed test (failure)
> Revision: d7680f13df105aa8fa0edbdf8efae31a5411f579
> Worker: gentoo-sparc
> Build Reason: (unknown)
> Blamelist: Jan Beulich <jbeulich@suse.com>
> 
> Steps:
> 
> - 0: worker_preparation ( success )
> 
> - 1: git checkout ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/1276/steps/1/logs/stdio
> 
> - 2: rm -rf binutils-build ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/1276/steps/2/logs/stdio
> 
> - 3: configure ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/1276/steps/3/logs/stdio
>         - config.log: https://builder.sourceware.org/buildbot/#builders/228/builds/1276/steps/3/logs/config_log
> 
> - 4: make ( warnings )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/1276/steps/4/logs/stdio
>         - warnings (21): https://builder.sourceware.org/buildbot/#builders/228/builds/1276/steps/4/logs/warnings__21_
> 
> - 5: make check ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/1276/steps/5/logs/stdio

Iirc I pointed out before that there appears to be an issue with the builder
here: "command timed out: 1200 seconds without output running". I don't think
the failure has anything to do with the changes committed earlier.

Jan

       reply	other threads:[~2023-09-14  8:59 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230914084342.10CE138555A9@sourceware.org>
2023-09-14  8:58 ` Jan Beulich [this message]
2023-09-14 18:33   ` Mark Wielaard
2024-04-27  1:03 builder
  -- strict thread matches above, loose matches on Subject: below --
2024-04-20  1:18 builder
2024-04-19 22:16 builder
2024-04-19  3:32 builder
2024-04-12  6:06 builder
2024-04-03 20:45 builder
2024-02-27  5:20 builder
2024-02-27  5:03 builder
2024-01-26 12:15 builder
2024-01-10 12:28 builder
2023-12-29 12:19 builder
2023-12-29  4:32 builder
2023-12-29  3:57 builder
2023-12-29  3:47 builder
2023-12-13  6:51 builder
2023-10-13  0:42 builder
2023-10-16  6:48 ` Jan Beulich
2023-10-19 11:23   ` Mark Wielaard
2023-10-19 11:48     ` Jan Beulich
2023-10-10 12:24 builder
2023-10-09 17:33 builder
2023-10-08  3:07 builder
2023-10-06  0:36 builder
2023-10-05 14:02 builder
2023-10-03  0:40 builder
2023-09-29 15:32 builder
2023-09-29  0:36 builder
2023-09-27 17:01 builder
2023-09-27  9:53 builder
2023-09-26 14:41 builder
2023-09-18  8:14 builder
2023-09-18  9:04 ` Sam James
2023-09-14  8:43 builder
     [not found] <20230818215458.6F9403858D32@sourceware.org>
2023-08-21  6:25 ` Jan Beulich
2023-08-21  8:57   ` Mark Wielaard
2023-08-18 21:54 builder
2023-08-01 14:33 builder
2023-07-17 20:31 builder
2023-07-17 16:50 builder
2023-07-17  8:19 builder
2023-07-07 10:47 builder
     [not found] <20230704171241.36F7E3858C31@sourceware.org>
2023-07-05  7:19 ` Jan Beulich
2023-07-05  9:39   ` Mark Wielaard
2023-07-04 17:12 builder
2023-06-30  5:04 builder
2023-06-29 20:25 builder
2023-06-27 23:59 builder
2023-06-14  5:36 builder
2023-06-11  0:39 builder
2023-06-07 22:58 builder
2023-06-08  0:08 ` Indu Bhagat
2023-06-08  0:25   ` Mark Wielaard
     [not found] <20230530134911.4B9523858D28@sourceware.org>
2023-06-06  7:02 ` mengqinggang
2023-06-05 16:17 builder
2023-06-05  4:39 builder
2023-05-30 13:49 builder
2023-05-30  5:12 builder
2023-05-19  7:36 builder
2023-05-07  0:40 builder
2023-05-03 15:12 builder
2023-05-03  6:48 builder
2023-03-07 15:07 builder
2023-03-05  0:19 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=a9f74fed-ac22-c5be-9aad-0118a856b681@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=builder@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).