public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: gdb-testers@sourceware.org Subject: ☠ Buildbot (Sourceware): binutils-gdb - failed compile (failure) (master) Date: Tue, 14 Feb 2023 01:50:54 +0000 [thread overview] Message-ID: <20230214015054.CF5563858D20@sourceware.org> (raw) A new failure has been detected on builder gdb-centos-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/71/builds/2945 Build state: failed compile (failure) Revision: 81ae560ca4f0da47729dc37a889c2f2e01c4c84e Worker: centos-x86_64 Build Reason: (unknown) Blamelist: Tom Tromey <tom@tromey.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/71/builds/2945/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/71/builds/2945/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/71/builds/2945/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/71/builds/2945/steps/3/logs/config_log - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/71/builds/2945/steps/4/logs/stdio - warnings (64): https://builder.sourceware.org/buildbot/#builders/71/builds/2945/steps/4/logs/warnings__64_
next reply other threads:[~2023-02-14 1:50 UTC|newest] Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-14 1:50 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-21 19:53 builder 2024-04-22 8:02 ` Mark Wielaard 2024-04-22 13:12 ` Tom Tromey 2024-04-03 15:00 builder 2024-03-25 22:35 builder 2024-03-25 20:31 builder 2024-03-25 20:27 builder 2024-01-29 19:39 builder 2024-01-22 20:26 builder 2024-01-16 7:36 builder 2024-01-16 7:04 builder 2024-01-15 20:47 builder 2023-12-29 9:19 builder 2023-12-08 4:54 builder 2023-11-24 9:05 builder 2023-11-22 2:13 builder 2023-11-22 1:06 builder 2023-10-06 20:20 builder 2023-09-25 14:20 builder 2023-09-25 9:35 builder 2023-09-25 8:56 builder 2023-08-25 20:10 builder 2023-08-21 17:29 builder 2023-08-19 7:17 builder 2023-08-18 17:49 builder 2023-08-11 7:43 builder 2023-08-02 9:36 builder 2023-07-21 11:58 builder 2023-06-05 17:50 builder 2023-05-26 9:07 builder 2023-05-23 20:15 builder 2023-05-16 9:50 builder 2023-05-12 20:21 builder 2023-05-05 17:39 builder 2023-05-02 16:24 builder 2023-05-01 20:08 builder 2023-05-01 5:55 builder 2023-04-29 7:07 builder 2023-04-28 17:35 builder 2023-04-27 13:27 builder 2023-04-27 0:36 builder 2023-04-26 17:35 builder 2023-04-26 6:13 builder 2023-04-24 20:24 builder 2023-04-24 14:38 builder 2023-04-24 0:29 builder 2023-04-21 14:02 builder 2023-04-21 3:59 builder 2023-04-14 21:36 builder 2023-04-13 20:24 builder 2023-04-07 0:28 builder 2023-04-06 0:46 builder 2023-04-03 14:09 builder 2023-03-30 22:05 builder 2023-03-28 22:47 builder 2023-03-27 15:38 builder 2023-03-23 7:56 builder 2023-03-22 21:46 builder 2023-03-20 8:45 builder 2023-03-18 21:44 builder 2023-03-18 19:15 builder 2023-03-15 18:42 builder 2023-03-10 16:23 builder 2023-03-07 10:45 builder 2023-03-06 0:28 builder 2023-02-28 12:34 builder 2023-02-28 12:13 builder 2023-02-27 15:15 builder 2023-02-25 10:45 builder 2023-02-24 20:13 builder 2023-02-20 22:05 builder 2023-02-17 1:11 builder 2023-02-14 19:22 builder 2023-02-14 6:07 builder 2023-02-11 3:21 builder 2023-02-09 19:26 builder 2023-02-09 0:59 builder 2023-01-30 20:40 builder 2023-01-26 16:42 builder 2023-01-25 13:05 builder 2023-01-23 20:34 builder 2023-01-19 0:23 builder 2023-01-17 14:32 builder 2023-01-17 11:48 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=20230214015054.CF5563858D20@sourceware.org \ --to=builder@sourceware.org \ --cc=gdb-testers@sourceware.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: 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).