public inbox for gcc-testresults@sourceware.org
help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: builder@sourceware.org
Cc: gcc-testresults@gcc.gnu.org
Subject: Re: ☠ Buildbot (Sourceware): gcc-autoregen - failed compile (failure) (master)
Date: Tue, 18 Jun 2024 14:23:52 -0400	[thread overview]
Message-ID: <4577acd43a4198dfcaabb6e71c4b85d6160bd87d.camel@redhat.com> (raw)
In-Reply-To: <20240618180628.856693882AEC@sourceware.org>

On Tue, 2024-06-18 at 18:06 +0000, builder@sourceware.org wrote:
> A new failure has been detected on builder gcc-autoregen while
> building gcc.
> 
> Full details are available at:
>    
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5931
> 
> Build state: failed compile (failure)
> Revision: c371d7bdbe69201b4c91179ff6f3e2237e0e7fbe
> Worker: bb2-1
> Build Reason: (unknown)
> Blamelist: David Malcolm <dmalcolm@redhat.com>

Sorry about this, the next patch should fix the build; see:

https://gcc.gnu.org/pipermail/gcc-patches/2024-June/655008.html


Dave

> 
> Steps:
> 
> - 0: worker_preparation ( success )
> 
> - 1: git checkout ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5931/steps/1/logs/stdio
> 
> - 2: autoregen.py ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5931/steps/2/logs/stdio
> 
> - 3: git diff ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5931/steps/3/logs/stdio
> 
> - 4: mkdir objdir ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5931/steps/4/logs/stdio
> 
> - 5: configure ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5931/steps/5/logs/stdio
> 
> - 6: make html ( failure )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5931/steps/6/logs/stdio
>         - warnings (68):
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5931/steps/6/logs/warnings__68_
> 


  reply	other threads:[~2024-06-18 18:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 18:06 builder
2024-06-18 18:23 ` David Malcolm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-26 16:49 builder
2024-06-20 12:42 builder
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=4577acd43a4198dfcaabb6e71c4b85d6160bd87d.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=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).