public inbox for gcc-testresults@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: "Nathaniel Shead" <nathanieloshead@gmail.com>
Cc: gcc-testresults@gcc.gnu.org
Subject: ☠ Buildbot (Sourceware): gcc-autoregen - failed compile (failure) (master)
Date: Fri, 27 Sep 2024 04:28:05 +0000	[thread overview]
Message-ID: <20240927042805.82C943858406@sourceware.org> (raw)

A failed build has been detected on builder gcc-autoregen while building gcc.

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

Build state: failed compile (failure)
Revision: ad08ef098a8c8bb9c148d0a32e91456fdf58ffc1
Worker: x3d1
Build Reason: (unknown)
Blamelist: Nathaniel Shead <nathanieloshead@gmail.com>

Steps:

- 0: worker_preparation ( success )

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

- 2: autoregen.py ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/8457/steps/2/logs/stdio

- 3: git diff ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/8457/steps/3/logs/stdio

- 4: mkdir objdir ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/8457/steps/4/logs/stdio

- 5: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/8457/steps/5/logs/stdio

- 6: make html ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/8457/steps/6/logs/stdio
        - warnings (27): https://builder.sourceware.org/buildbot/#/builders/269/builds/8457/steps/6/logs/warnings__27_


             reply	other threads:[~2024-09-27  4:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  4:28 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-27 14:29 builder
2024-09-26  2:32 builder
2024-09-23 23:37 builder
2024-09-20 15:43 builder
2024-09-03  8:49 builder
2024-09-03  7:39 builder
2024-09-03  7:31 builder
2024-08-01 21:41 builder
2024-07-28 23:52 builder
2024-07-20 23:18 builder
2024-07-09 22:19 builder
2024-07-09 21:21 builder
2024-07-09  1:53 builder
2024-06-26 16:49 builder
2024-06-20 12:42 builder
2024-06-18 18:06 builder
2024-06-18 18:23 ` David Malcolm
2024-06-13 19:04 builder
2024-06-13 11:53 builder
2024-06-10 17:41 builder
2024-06-05 17:58 builder
2024-06-03 20:27 builder
2024-05-29 14:06 builder
2024-05-20  8:56 builder
2024-03-18 10:00 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=20240927042805.82C943858406@sourceware.org \
    --to=builder@sourceware.org \
    --cc=gcc-testresults@gcc.gnu.org \
    --cc=nathanieloshead@gmail.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).