public inbox for gcc-testresults@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: gcc-testresults@gcc.gnu.org
Subject: ☠ Buildbot (Sourceware): gcc - failed update (failure) (master)
Date: Fri, 28 Apr 2023 13:52:46 +0000	[thread overview]
Message-ID: <20230428135246.8B78B3858CDB@sourceware.org> (raw)

A new failure has been detected on builder gcc-rawhide-x86_64 while building gcc.

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

Build state: failed update (failure)
Revision: (unknown)
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Roger Sayle <roger@nextmovesoftware.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/158/builds/3509/steps/1/logs/stdio

A restored build has been detected on builder gcc-fedora-x86_64 while building gcc.

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

Build state: build successful
Revision: 650c36ec461a722d9c65e82512b4c3aeec2ffee1
Worker: bbo1-1
Build Reason: (unknown)
Blamelist: Roger Sayle <roger@nextmovesoftware.com>

Steps:

- 0: worker_preparation ( success )

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

- 2: rm -rf gcc-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/159/builds/4033/steps/2/logs/stdio

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

- 4: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/159/builds/4033/steps/4/logs/stdio
        - warnings (318): https://builder.sourceware.org/buildbot/#builders/159/builds/4033/steps/4/logs/warnings__318_

- 5: rm -rf gcc-build_1 ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/159/builds/4033/steps/5/logs/stdio


             reply	other threads:[~2023-04-28 13:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 13:52 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-07 19:49 builder
2024-03-14 16:26 builder
2024-01-27 17:15 builder
2023-11-14 15:42 builder
2023-10-30 21:18 builder
2023-08-14 14:22 builder
2023-05-11  8:18 builder
2023-04-28 14:51 builder
2023-04-28 14:50 builder
2023-04-28 13:37 builder
2023-04-28 12:39 builder
2023-04-28 12:08 builder
2023-04-28 12:03 builder
2023-03-24 13:24 builder
2023-03-24  9:52 builder
2023-03-24  9:29 builder
2023-03-24  3:00 builder
2023-02-21 14:55 builder
2023-01-31 13:21 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=20230428135246.8B78B3858CDB@sourceware.org \
    --to=builder@sourceware.org \
    --cc=gcc-testresults@gcc.gnu.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).