public inbox for gcc-testresults@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: "Christophe Lyon" <christophe.lyon@linaro.org>, "GCC Administrator" <gccadmin@gcc.gnu.org>, "H.J. Lu" <hjl.tools@gmail.com>, "Hans-Peter Nilsson" <hp@axis.com>, "Jakub Jelinek" <jakub@redhat.com>, "Jørgen Kvalsvik" <j@lambda.is>, "Martin Jambor" <mjambor@suse.cz>, "Richard Biener" <rguenther@suse.de>, "Tobias Burnus" <tburnus@baylibre.com>, "Vladimir N. Makarov" <vmakarov@redhat.com>, "Wilco Dijkstra" <wilco.dijkstra@arm.com>, centurion <centurion009@proton.me> Cc: gcc-testresults@gcc.gnu.org Subject: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master) Date: Fri, 05 Apr 2024 09:48:48 +0000 [thread overview] Message-ID: <20240405094848.19ECC3858C24@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/4161 Build state: failed 'git diff ...' (failure) Revision: 9ab8fdfeef5b1a47b358e08a98177b2fad65fed9 Worker: bb2-1 Build Reason: (unknown) Blamelist: Christophe Lyon <christophe.lyon@linaro.org>, GCC Administrator <gccadmin@gcc.gnu.org>, H.J. Lu <hjl.tools@gmail.com>, Hans-Peter Nilsson <hp@axis.com>, Jakub Jelinek <jakub@redhat.com>, Jørgen Kvalsvik <j@lambda.is>, Martin Jambor <mjambor@suse.cz>, Richard Biener <rguenther@suse.de>, Tobias Burnus <tburnus@baylibre.com>, Vladimir N. Makarov <vmakarov@redhat.com>, Wilco Dijkstra <wilco.dijkstra@arm.com>, centurion <centurion009@proton.me> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4161/steps/1/logs/stdio - 2: autoregen.py ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4161/steps/2/logs/stdio - 3: git diff ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/269/builds/4161/steps/3/logs/stdio
next reply other threads:[~2024-04-05 9:48 UTC|newest] Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-05 9:48 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-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 21:10 builder 2024-05-17 22:03 ` David Malcolm 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-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=20240405094848.19ECC3858C24@sourceware.org \ --to=builder@sourceware.org \ --cc=centurion009@proton.me \ --cc=christophe.lyon@linaro.org \ --cc=gcc-testresults@gcc.gnu.org \ --cc=gccadmin@gcc.gnu.org \ --cc=hjl.tools@gmail.com \ --cc=hp@axis.com \ --cc=j@lambda.is \ --cc=jakub@redhat.com \ --cc=mjambor@suse.cz \ --cc=rguenther@suse.de \ --cc=tburnus@baylibre.com \ --cc=vmakarov@redhat.com \ --cc=wilco.dijkstra@arm.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: 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).