public inbox for gccadmin@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: "Ajit Kumar Agarwal" <aagarwa1@linux.ibm.com>,
	"Aldy Hernandez" <aldyh@redhat.com>,
	"Alex Coplan" <alex.coplan@arm.com>,
	"Andrew Pinski" <quic_apinski@quicinc.com>,
	"Christoph Müllner" <christoph.muellner@vrull.eu>,
	"Dimitar Dimitrov" <dimitar@dinux.eu>,
	"Eric Botcazou" <ebotcazou@adacore.com>,
	"GCC Administrator" <gccadmin@gcc.gnu.org>,
	"Gaius Mulley" <gaiusmod2@gmail.com>,
	"Georg-Johann Lay" <avr@gjlay.de>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	"Hans-Peter Nilsson" <hp@bitrange.com>,
	Hu@sourceware.org, "Jakub Jelinek" <jakub@redhat.com>,
	"Jeff Law" <jlaw@ventanamicro.com>,
	"Jose E. Marchesi" <jose.marchesi@oracle.com>,
	"Ken Matsui" <kmatsui@gcc.gnu.org>,
	"Kito Cheng" <kito.cheng@sifive.com>,
	"Marek Polacek" <polacek@redhat.com>,
	"Martin Jambor" <mjambor@suse.cz>,
	"Nathaniel Shead" <nathanieloshead@gmail.com>,
	"Pan Li" <pan2.li@intel.com>,
	"Richard Biener" <rguenther@suse.de>,
	"Roger Sayle" <roger@nextmovesoftware.com>,
	"Stefan Schulze Frielinghaus" <stefansf@linux.ibm.com>,
	"Vladimir N. Makarov" <vmakarov@redhat.com>,
	"Xi Ruoyao" <xry111@xry111.site>,
	"Xiao Zeng" <zengxiao@eswincomputing.com>,
	"YunQiang Su" <syq@gcc.gnu.org>,
	"Zac Walker" <zacwalker@microsoft.com>,
	konglin1 <lingling.kong@intel.com>
Cc: gcc-testresults@gcc.gnu.org
Subject: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master)
Date: Sat, 11 May 2024 01:55:20 +0000	[thread overview]
Message-ID: <20240511015520.1C4E8386F81A@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/4876

Build state: failed 'git diff ...' (failure)
Revision: 85c2ba4244196dcccdf0647ff49f376c52513f65
Worker: bb2-2
Build Reason: (unknown)
Blamelist: Ajit Kumar Agarwal <aagarwa1@linux.ibm.com>, Aldy Hernandez <aldyh@redhat.com>, Alex Coplan <alex.coplan@arm.com>, Andrew Pinski <quic_apinski@quicinc.com>, Christoph Müllner <christoph.muellner@vrull.eu>, Dimitar Dimitrov <dimitar@dinux.eu>, Eric Botcazou <ebotcazou@adacore.com>, GCC Administrator <gccadmin@gcc.gnu.org>, Gaius Mulley <gaiusmod2@gmail.com>, Georg-Johann Lay <avr@gjlay.de>, H.J. Lu <hjl.tools@gmail.com>, Hans-Peter Nilsson <hp@bitrange.com>, Hu, Lin1 <lin1.hu@intel.com>, Jakub Jelinek <jakub@redhat.com>, Jeff Law <jlaw@ventanamicro.com>, Jose E. Marchesi <jose.marchesi@oracle.com>, Ken Matsui <kmatsui@gcc.gnu.org>, Kito Cheng <kito.cheng@sifive.com>, Marek Polacek <polacek@redhat.com>, Martin Jambor <mjambor@suse.cz>, Nathaniel Shead <nathanieloshead@gmail.com>, Pan Li <pan2.li@intel.com>, Richard Biener <rguenther@suse.de>, Roger Sayle <roger@nextmovesoftware.com>, Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>, Vladimir N. Makarov <vmakarov@redhat.com>, Xi Ruoyao <xry111@xry111.site>, Xiao Zeng <zengxiao@eswincomputing.com>, YunQiang Su <syq@gcc.gnu.org>, Zac Walker <zacwalker@microsoft.com>, konglin1 <lingling.kong@intel.com>

Steps:

- 0: worker_preparation ( success )

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

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

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

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

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

- 6: make html ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4876/steps/6/logs/stdio
        - warnings (67): https://builder.sourceware.org/buildbot/#/builders/269/builds/4876/steps/6/logs/warnings__67_

- 7: make regenerate-opt-urls ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4876/steps/7/logs/stdio

- 8: git diff_1 ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4876/steps/8/logs/stdio


             reply	other threads:[~2024-05-11  1:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11  1:55 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-28 12:43 builder
2024-05-28  0:58 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-11  1:54 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-05  9:48 builder
2024-04-03 12:43 builder
2024-04-01  1:44 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
2023-12-01  7:14 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=20240511015520.1C4E8386F81A@sourceware.org \
    --to=builder@sourceware.org \
    --cc=Hu@sourceware.org \
    --cc=aagarwa1@linux.ibm.com \
    --cc=aldyh@redhat.com \
    --cc=alex.coplan@arm.com \
    --cc=avr@gjlay.de \
    --cc=christoph.muellner@vrull.eu \
    --cc=dimitar@dinux.eu \
    --cc=ebotcazou@adacore.com \
    --cc=gaiusmod2@gmail.com \
    --cc=gcc-testresults@gcc.gnu.org \
    --cc=gccadmin@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=hp@bitrange.com \
    --cc=jakub@redhat.com \
    --cc=jlaw@ventanamicro.com \
    --cc=jose.marchesi@oracle.com \
    --cc=kito.cheng@sifive.com \
    --cc=kmatsui@gcc.gnu.org \
    --cc=lingling.kong@intel.com \
    --cc=mjambor@suse.cz \
    --cc=nathanieloshead@gmail.com \
    --cc=pan2.li@intel.com \
    --cc=polacek@redhat.com \
    --cc=quic_apinski@quicinc.com \
    --cc=rguenther@suse.de \
    --cc=roger@nextmovesoftware.com \
    --cc=stefansf@linux.ibm.com \
    --cc=syq@gcc.gnu.org \
    --cc=vmakarov@redhat.com \
    --cc=xry111@xry111.site \
    --cc=zacwalker@microsoft.com \
    --cc=zengxiao@eswincomputing.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).