public inbox for gccadmin@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: "Andre Vieira" <andre.simoesdiasvieira@arm.com>, "Christophe Lyon" <christophe.lyon@linaro.org>, "David Faust" <david.faust@oracle.com>, "GCC Administrator" <gccadmin@gcc.gnu.org>, "Gaius Mulley" <gaiusmod2@gmail.com>, "H.J. Lu" <hjl.tools@gmail.com>, "Hongyu Wang" <hongyu.wang@intel.com>, "Jakub Jelinek" <jakub@redhat.com>, "Jonathan Wakely" <jwakely@redhat.com>, "Joseph Myers" <josmyers@redhat.com>, "Juergen Christ" <jchrist@linux.ibm.com>, "Jørgen Kvalsvik" <j@lambda.is>, "Kewen Lin" <linkw@linux.ibm.com>, "Martin Jambor" <mjambor@suse.cz>, "Nathaniel Shead" <nathanieloshead@gmail.com>, "Paul Thomas" <pault@gcc.gnu.org>, "Peter Bergner" <bergner@linux.ibm.com>, "Richard Ball" <richard.ball@arm.com>, "Richard Biener" <rguenther@suse.de>, "Richard Sandiford" <richard.sandiford@arm.com>, "Sebastian Huber" <sebastian.huber@embedded-brains.de>, "Sergey Bugaev" <bugaevc@gmail.com>, "Tatsuyuki Ishi" <ishitatsuyuki@gmail.com>, "Thomas Schwinge" <tschwinge@baylibre.com>, "Tobias Burnus" <tburnus@baylibre.com>, "Uros Bizjak" <ubizjak@gmail.com>, "Yang Yujie" <yangyujie@loongson.cn> Cc: gcc-testresults@gcc.gnu.org Subject: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master) Date: Wed, 10 Apr 2024 17:21:19 +0000 [thread overview] Message-ID: <20240410172119.0A9903885C23@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/4248 Build state: failed 'git diff ...' (failure) Revision: 3a787e038fe3549d6ec9ec9aa6416dcbba664fd9 Worker: bb1-2 Build Reason: (unknown) Blamelist: Andre Vieira <andre.simoesdiasvieira@arm.com>, Christophe Lyon <christophe.lyon@linaro.org>, David Faust <david.faust@oracle.com>, GCC Administrator <gccadmin@gcc.gnu.org>, Gaius Mulley <gaiusmod2@gmail.com>, H.J. Lu <hjl.tools@gmail.com>, Hongyu Wang <hongyu.wang@intel.com>, Jakub Jelinek <jakub@redhat.com>, Jonathan Wakely <jwakely@redhat.com>, Joseph Myers <josmyers@redhat.com>, Juergen Christ <jchrist@linux.ibm.com>, Jørgen Kvalsvik <j@lambda.is>, Kewen Lin <linkw@linux.ibm.com>, Martin Jambor <mjambor@suse.cz>, Nathaniel Shead <nathanieloshead@gmail.com>, Paul Thomas <pault@gcc.gnu.org>, Peter Bergner <bergner@linux.ibm.com>, Richard Ball <richard.ball@arm.com>, Richard Biener <rguenther@suse.de>, Richard Sandiford <richard.sandiford@arm.com>, Sebastian Huber <sebastian.huber@embedded-brains.de>, Sergey Bugaev <bugaevc@gmail.com>, Tatsuyuki Ishi <ishitatsuyuki@gmail.com>, Thomas Schwinge <tschwinge@baylibre.com>, Tobias Burnus <tburnus@baylibre.com>, Uros Bizjak <ubizjak@gmail.com>, Yang Yujie <yangyujie@loongson.cn> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/1/logs/stdio - 2: autoregen.py ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/2/logs/stdio - 3: git diff ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/3/logs/stdio - 4: mkdir objdir ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/4/logs/stdio - 5: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/5/logs/stdio - 6: make html ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/6/logs/stdio - warnings (67): https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/6/logs/warnings__67_ - 7: make regenerate-opt-urls ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/7/logs/stdio - 8: git diff_1 ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4248/steps/8/logs/stdio
next reply other threads:[~2024-04-10 17:21 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-10 17:21 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 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-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=20240410172119.0A9903885C23@sourceware.org \ --to=builder@sourceware.org \ --cc=andre.simoesdiasvieira@arm.com \ --cc=bergner@linux.ibm.com \ --cc=bugaevc@gmail.com \ --cc=christophe.lyon@linaro.org \ --cc=david.faust@oracle.com \ --cc=gaiusmod2@gmail.com \ --cc=gcc-testresults@gcc.gnu.org \ --cc=gccadmin@gcc.gnu.org \ --cc=hjl.tools@gmail.com \ --cc=hongyu.wang@intel.com \ --cc=ishitatsuyuki@gmail.com \ --cc=j@lambda.is \ --cc=jakub@redhat.com \ --cc=jchrist@linux.ibm.com \ --cc=josmyers@redhat.com \ --cc=jwakely@redhat.com \ --cc=linkw@linux.ibm.com \ --cc=mjambor@suse.cz \ --cc=nathanieloshead@gmail.com \ --cc=pault@gcc.gnu.org \ --cc=rguenther@suse.de \ --cc=richard.ball@arm.com \ --cc=richard.sandiford@arm.com \ --cc=sebastian.huber@embedded-brains.de \ --cc=tburnus@baylibre.com \ --cc=tschwinge@baylibre.com \ --cc=ubizjak@gmail.com \ --cc=yangyujie@loongson.cn \ /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: linkBe 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).