From: Jerry D <jvdelisle2@gmail.com>
To: gfortran <fortran@gcc.gnu.org>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Fwd: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Sun, 29 Jan 2023 11:36:42 -0800 [thread overview]
Message-ID: <1985b16e-f17d-bba6-8b57-d372f1741356@gmail.com> (raw)
In-Reply-To: <20230129193123.51BDE3858D35@sourceware.org>
I had this show up today. I have no idea what this is about.
Please advise.
Jerry
-------- Forwarded Message --------
Subject: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Sun, 29 Jan 2023 19:31:23 +0000
From: builder@sourceware.org
To: Jerry DeLisle <jvdelisle@gcc.gnu.org>
A new failure has been detected on builder gcc-gentoo-sparc while
building gcc.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/231/builds/210
Build state: failed configure (failure)
Revision: 8011fbba7baa46947341ca8069b5a327163a68d5
Worker: gentoo-sparc-big
Build Reason: (unknown)
Blamelist: Jerry DeLisle <jvdelisle@gcc.gnu.org>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio:
https://builder.sourceware.org/buildbot/#builders/231/builds/210/steps/1/logs/stdio
- 2: rm -rf gcc-build ( success )
Logs:
- stdio:
https://builder.sourceware.org/buildbot/#builders/231/builds/210/steps/2/logs/stdio
- 3: configure ( failure )
Logs:
- stdio:
https://builder.sourceware.org/buildbot/#builders/231/builds/210/steps/3/logs/stdio
next parent reply other threads:[~2023-01-29 19:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230129193123.51BDE3858D35@sourceware.org>
2023-01-29 19:36 ` Jerry D [this message]
2023-01-29 19:43 ` NightStrike
2023-01-29 19:49 ` Sam James
2023-01-30 6:27 ` Steve Kargl
2023-01-30 13:46 ` Sam James
2023-01-31 2:31 ` Jerry D
2023-01-30 13:52 ` Mark Wielaard
2023-01-30 14:46 ` Thomas Koenig
2023-01-30 15:10 ` Steve Kargl
2023-01-30 22:07 ` Gerald Pfeifer
2023-01-30 22:44 ` Thomas Koenig
2023-01-30 22:50 ` Steve Kargl
2023-01-31 13:13 ` Thomas Schwinge
2023-01-31 14:38 ` LIU Hao
2023-01-31 20:18 ` Steve Kargl
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=1985b16e-f17d-bba6-8b57-d372f1741356@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@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).