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 '(set -e; ...' (exception) (master)
Date: Wed, 20 Mar 2024 17:11:34 +0000	[thread overview]
Message-ID: <20240320171134.39AEB3858D1E@sourceware.org> (raw)

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

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

Build state: retry lost connection '(set -e; ...' (exception)
Revision: 105470cd79f6d8c62b9156ce45e992895b01b13b
Worker: debian-ppc64
Build Reason: (unknown)
Blamelist: Hannes Domani <ssbssa@yahoo.de>

Steps:

- 0: worker_preparation ( success )

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

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

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

- 4: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/4/logs/stdio
        - warnings (28): https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/4/logs/warnings__28_

- 5: make check-gdb ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/5/logs/stdio
        - gdb.sum: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/5/logs/gdb_sum
        - gdb.log: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/5/logs/gdb_log

- 6: prep ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/6/logs/stdio

- 7: build bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/7/logs/stdio

- 8: fetch bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/8/logs/stdio

- 9: unpack bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/9/logs/stdio

- 10: pass .bunsen.source.gitname ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/10/logs/stdio

- 11: pass .bunsen.source.gitdescribe ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/11/logs/stdio

- 12: pass .bunsen.source.gitbranch ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/12/logs/stdio

- 13: pass .bunsen.source.gitrepo ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/13/logs/stdio

- 14: upload to bunsen ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/14/logs/stdio

- 15: clean up ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/15/logs/stdio

- 16: make check-gdb_1 ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/16/logs/stdio
        - gdb.sum: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/16/logs/gdb_sum
        - gdb.log: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/16/logs/gdb_log

- 17: prep_1 ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/17/logs/stdio

- 18: build bunsen.cpio.gz_1 ( exception )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/18/logs/stdio
        - cancelled: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/18/logs/cancelled
        - err.text: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/18/logs/err_text
        - err.html: https://builder.sourceware.org/buildbot/#/builders/76/builds/6431/steps/18/logs/err_html


             reply	other threads:[~2024-03-20 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 17:11 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-17 13:29 builder
2024-01-09 13:18 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=20240320171134.39AEB3858D1E@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).