public inbox for gdbadmin@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: "Andrew Burgess" <aburgess@redhat.com>, "Bernd Edlinger" <bernd.edlinger@hotmail.de>, "GDB Administrator" <gdbadmin@sourceware.org>, "Pedro Alves" <pedro@palves.net>, "Sébastien Michelland" <sebastien.michelland@lcis.grenoble-inp.fr> Subject: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) (master) Date: Sat, 27 Apr 2024 01:03:11 +0000 [thread overview] Message-ID: <20240427010311.A5C603858C42@sourceware.org> (raw) A new failure has been detected on builder binutils-rawhide-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393 Build state: failed test (failure) Revision: 94f7532ed2eba5251e5c2b8868563f1169ad5b6d Worker: bb2-1 Build Reason: (unknown) Blamelist: Andrew Burgess <aburgess@redhat.com>, Bernd Edlinger <bernd.edlinger@hotmail.de>, GDB Administrator <gdbadmin@sourceware.org>, Pedro Alves <pedro@palves.net>, Sébastien Michelland <sebastien.michelland@lcis.grenoble-inp.fr> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/1/logs/stdio - 2: rm -rf binutils-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/3/logs/config_log - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/4/logs/stdio - warnings (72): https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/4/logs/warnings__72_ - 5: make check ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/stdio - ld.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/ld_sum - ld.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/ld_log - gas.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/gas_sum - gas.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/gas_log - binutils.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/binutils_sum - binutils.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/binutils_log - libsframe.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/libsframe_sum - libsframe.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/libsframe_log - libctf.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/libctf_sum - libctf.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/libctf_log - warnings (15): https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/5/logs/warnings__15_ - 6: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/6/logs/stdio - 7: build bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/7/logs/stdio - 8: fetch bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/8/logs/stdio - 9: unpack bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/9/logs/stdio - 10: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/10/logs/stdio - 11: pass .bunsen.source.gitdescribe ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/15/logs/stdio - 16: rm -rf binutils-build_1 ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3393/steps/16/logs/stdio
next reply other threads:[~2024-04-27 1:03 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-27 1:03 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-12 6:06 builder 2024-01-26 12:15 builder 2023-12-29 4:32 builder 2023-10-13 0:42 builder 2023-10-06 0:36 builder 2023-10-03 0:40 builder 2023-09-29 0:36 builder 2023-09-18 8:14 builder 2023-08-01 14:33 builder 2023-07-17 20:31 builder 2023-07-17 8:19 builder 2023-06-11 0:39 builder 2023-05-07 0:40 builder 2023-03-05 0:19 builder 2023-03-05 9:44 ` Mark Wielaard
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=20240427010311.A5C603858C42@sourceware.org \ --to=builder@sourceware.org \ --cc=aburgess@redhat.com \ --cc=bernd.edlinger@hotmail.de \ --cc=gdbadmin@sourceware.org \ --cc=pedro@palves.net \ --cc=sebastien.michelland@lcis.grenoble-inp.fr \ /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).