public inbox for gcc-testresults@sourceware.org
help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: builder@sourceware.org, Robin Dapp <rdapp@ventanamicro.com>,
	Tom Tromey <tromey@adacore.com>
Cc: gcc-testresults@gcc.gnu.org
Subject: Re: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master)
Date: Fri, 17 May 2024 18:03:57 -0400	[thread overview]
Message-ID: <109f12e1be1e5c3c6a5db4c11cfe5eadbc3ce4a8.camel@redhat.com> (raw)
In-Reply-To: <20240517211006.7C4C43858D20@sourceware.org>

On Fri, 2024-05-17 at 21:10 +0000, builder@sourceware.org wrote:
> 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/5142

Sorry about this; should be fixed by
  https://gcc.gnu.org/pipermail/gcc-patches/2024-May/652062.html

Dave

> 
> Build state: failed 'git diff ...' (failure)
> Revision: e0b9c8ad7098fb08a25a61fe17d4274dd73e5145
> Worker: bb1-2
> Build Reason: (unknown)
> Blamelist: David Malcolm <dmalcolm@redhat.com>, Robin Dapp
> <rdapp@ventanamicro.com>, Tom Tromey <tromey@adacore.com>
> 
> Steps:
> 
> - 0: worker_preparation ( success )
> 
> - 1: git checkout ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/1/logs/stdio
> 
> - 2: autoregen.py ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/2/logs/stdio
> 
> - 3: git diff ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/3/logs/stdio
> 
> - 4: mkdir objdir ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/4/logs/stdio
> 
> - 5: configure ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/5/logs/stdio
> 
> - 6: make html ( warnings )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/6/logs/stdio
>         - warnings (68):
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/6/logs/warnings__68_
> 
> - 7: make regenerate-opt-urls ( success )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/7/logs/stdio
> 
> - 8: git diff_1 ( failure )
>     Logs:
>         - stdio:
> https://builder.sourceware.org/buildbot/#/builders/269/builds/5142/steps/8/logs/stdio
> 


  reply	other threads:[~2024-05-17 22:04 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 21:10 builder
2024-05-17 22:03 ` David Malcolm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-06  7:07 builder
2024-06-06  1:03 builder
2024-06-05 20:41 builder
2024-06-06  6:47 ` Jonathan Wakely
2024-06-05 20:28 builder
2024-05-28 12:43 builder
2024-05-28  0:58 builder
2024-05-27  4:20 builder
2024-05-20  9:58 builder
2024-05-20  9:42 builder
2024-05-20  9:37 builder
2024-05-20  6:44 builder
2024-05-18 21:30 builder
2024-05-17 19:26 builder
2024-05-11  1:55 builder
2024-05-11  1:54 builder
2024-05-08 15:08 builder
2024-05-08  9:01 builder
2024-05-07 17:04 builder
2024-05-07 17:04 builder
2024-05-07 16:44 builder
2024-05-02 13:50 builder
2024-04-15 18:45 builder
2024-04-15 18:37 builder
2024-04-15 16:12 builder
2024-04-15 13:40 builder
2024-04-15 11:31 builder
2024-04-15 11:25 builder
2024-04-15 11:09 builder
2024-04-12 23:47 builder
2024-04-12 19:52 builder
2024-04-12 18:59 builder
2024-04-12  5:14 builder
2024-04-11 10:34 builder
2024-04-11 10:34 builder
2024-04-11  1:17 builder
2024-04-10 17:21 builder
2024-04-09 17:23 builder
2024-04-09  7:54 builder
2024-04-09  7:48 builder
2024-04-09  3:16 builder
2024-04-08 20:17 builder
2024-04-08 14:37 builder
2024-04-05  9:48 builder
2024-04-04 21:38 builder
2024-04-04 18:50 builder
2024-04-03 12:43 builder
2024-04-02 11:54 builder
2024-04-02 11:54 builder
2024-04-02  6:20 builder
2024-04-01  1:47 builder
2024-04-01  1:44 builder
2024-03-15  7:07 builder
2024-03-15  7:01 builder
2024-03-08 15:10 builder
2024-03-08  9:06 builder
2024-01-05 20:59 builder
2024-01-05 20:58 builder
2024-01-05  2:30 builder
2024-01-05  3:49 ` Andrew Pinski
2024-01-06  0:28   ` Mark Wielaard
2024-01-04  1:34 builder
2024-01-03 13:53 builder
2023-12-08 11:32 builder
2023-12-01  7:14 builder
2023-11-30 14:50 builder
2023-11-30 10:22 builder
2023-11-30 10:21 builder
2023-11-30  9:11 builder
2023-11-15 17:29 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=109f12e1be1e5c3c6a5db4c11cfe5eadbc3ce4a8.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=builder@sourceware.org \
    --cc=gcc-testresults@gcc.gnu.org \
    --cc=rdapp@ventanamicro.com \
    --cc=tromey@adacore.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).