public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: gdb-testers@sourceware.org
Subject: ☝ Buildbot (Sourceware): binutils-gdb - retry lost connection compile (retry) (master)
Date: Tue, 09 Jan 2024 15:29:15 +0000	[thread overview]
Message-ID: <20240109152915.BD9233858C74@sourceware.org> (raw)

A retry build has been detected on builder gdb-debian-i386 while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#/builders/105/builds/5617

Build state: retry lost connection compile (retry)
Revision: 245703b3ce7522ddbf9290267129878ad8c6c725
Worker: debian-i386
Build Reason: (unknown)
Blamelist: Alan Modra <amodra@gmail.com>, Andrew Burgess <aburgess@redhat.com>, Carl Love <cel@linux.ibm.com>, Carl Love <cel@us.ibm.com>, Cui, Lili <lili.cui@intel.com>, Cupertino Miranda <cupertino.miranda@oracle.com>, Dimitar Dimitrov <dimitar@dinux.eu>, GDB Administrator <gdbadmin@sourceware.org>, Guinevere Larsen <blarsen@redhat.com>, H.J. Lu <hjl.tools@gmail.com>, Hu, Lin1 <lin1.hu@intel.com>, Indu Bhagat <indu.bhagat@oracle.com>, Jan Beulich <jbeulich@suse.com>, Jin Ma <jinma@linux.alibaba.com>, Joseph Myers <josmyers@redhat.com>, Joseph Myers <jsm@polyomino.org.uk>, Lulu Cai <cailulu@loongson.cn>, Mike Frysinger <vapier@gentoo.org>, Mo, Zewei <zewei.mo@intel.com>, Nelson Chu <nelson@rivosinc.com>, Nick Clifton <nickc@redhat.com>, Nils-Christian Kempke <nils-christian.kempke@intel.com>, Samuel Tardieu <sam@rfc1149.net>, Schimpe, Christina <christina.schimpe@intel.com>, Sergey Bugaev <bugaevc@gmail.com>, Tamar Christina <tamar.christina@arm.com>, Tejas Joshi <TejasSanjay.Joshi@amd.com>, Tom Tromey <tom@tromey.com>, Tom de Vries <tdevries@suse.de>, YunQiang Su <yunqiang.su@cipunited.com>, changjiachen <changjiachen@stu.xupt.edu.cn>, konglin1 <lingling.kong@intel.com>, mengqinggang <mengqinggang@loongson.cn>, srinath <srinath.parvathaneni@arm.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/5617/steps/1/logs/stdio

- 2: rm -rf gdb-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/5617/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/5617/steps/3/logs/stdio
        - config.log: https://builder.sourceware.org/buildbot/#/builders/105/builds/5617/steps/3/logs/config_log

- 4: make ( retry )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/5617/steps/4/logs/stdio
        - cancelled: https://builder.sourceware.org/buildbot/#/builders/105/builds/5617/steps/4/logs/cancelled

A retry build has been detected on builder gdb-rawhide-x86_64 while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#/builders/136/builds/5529

Build state: worker not available
Revision: (unknown)
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Tom Tromey <tom@tromey.com>

Steps:

- 0: worker_preparation ( exception )
    Logs:
        - err.text: https://builder.sourceware.org/buildbot/#/builders/136/builds/5529/steps/0/logs/err_text
        - err.html: https://builder.sourceware.org/buildbot/#/builders/136/builds/5529/steps/0/logs/err_html


             reply	other threads:[~2024-01-09 15:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 15:29 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-19  3:31 builder
2024-04-19  3:30 builder
2024-01-10 15:51 builder
2024-01-09 15:32 builder
2024-01-09 13:17 builder
2024-01-09  6:20 builder
2023-12-05  6:57 builder
2023-11-21 14:28 builder
2023-10-20  2:02 builder
2023-09-29 15:40 builder
2023-03-23 14:54 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=20240109152915.BD9233858C74@sourceware.org \
    --to=builder@sourceware.org \
    --cc=gdb-testers@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).