public inbox for gdbadmin@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: "Aditya Vidyadhar Kamath" <Aditya.Kamath1@ibm.com>, "Andrew Burgess" <aburgess@redhat.com>, "Andrew Carlotti" <andrew.carlotti@arm.com>, Cui@sourceware.org, "GDB Administrator" <gdbadmin@sourceware.org>, "H.J. Lu" <hjl.tools@gmail.com>, "Indu Bhagat" <indu.bhagat@oracle.com>, "Jan Beulich" <jbeulich@suse.com>, "Lulu Cai" <cailulu@loongson.cn>, "Mike Frysinger" <vapier@gentoo.org>, "Nick Clifton" <nickc@redhat.com>, "Saurabh Jha" <saurabh.jha@arm.com>, "Simon Marchi" <simon.marchi@efficios.com>, "Srinath Parvathaneni" <srinath.parvathaneni@arm.com>, "Tom Tromey" <tom@tromey.com>, "Tom Tromey" <tromey@adacore.com>, "Tom de Vries" <tdevries@suse.de>, "Victor Do Nascimento" <victor.donascimento@arm.com>, "Vladimir Mezentsev" <vladimir.mezentsev@oracle.com>, changjiachen <changjiachen@stu.xupt.edu.cn>, mengqinggang <mengqinggang@loongson.cn> Subject: ☠ Buildbot (Sourceware): binutils-gdb - failed configure (failure) (master) Date: Sat, 13 Jan 2024 01:21:59 +0000 [thread overview] Message-ID: <20240113012159.D085D3858D1E@sourceware.org> (raw) A new failure has been detected on builder gdb-ibm-power9 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/167/builds/5446 Build state: failed configure (failure) Revision: 98138c62cd7f721af132f9b24f274332fd8bf079 Worker: ibm_power9 Build Reason: (unknown) Blamelist: Aditya Vidyadhar Kamath <Aditya.Kamath1@ibm.com>, Andrew Burgess <aburgess@redhat.com>, Andrew Carlotti <andrew.carlotti@arm.com>, Cui, Lili <lili.cui@intel.com>, GDB Administrator <gdbadmin@sourceware.org>, H.J. Lu <hjl.tools@gmail.com>, Indu Bhagat <indu.bhagat@oracle.com>, Jan Beulich <jbeulich@suse.com>, Lulu Cai <cailulu@loongson.cn>, Mike Frysinger <vapier@gentoo.org>, Nick Clifton <nickc@redhat.com>, Saurabh Jha <saurabh.jha@arm.com>, Simon Marchi <simon.marchi@efficios.com>, Srinath Parvathaneni <srinath.parvathaneni@arm.com>, Tom Tromey <tom@tromey.com>, Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>, Victor Do Nascimento <victor.donascimento@arm.com>, Vladimir Mezentsev <vladimir.mezentsev@oracle.com>, changjiachen <changjiachen@stu.xupt.edu.cn>, mengqinggang <mengqinggang@loongson.cn> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/167/builds/5446/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/167/builds/5446/steps/2/logs/stdio - 3: configure ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/167/builds/5446/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#/builders/167/builds/5446/steps/3/logs/config_log
reply other threads:[~2024-01-13 1:21 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240113012159.D085D3858D1E@sourceware.org \ --to=builder@sourceware.org \ --cc=Aditya.Kamath1@ibm.com \ --cc=Cui@sourceware.org \ --cc=aburgess@redhat.com \ --cc=andrew.carlotti@arm.com \ --cc=cailulu@loongson.cn \ --cc=changjiachen@stu.xupt.edu.cn \ --cc=gdbadmin@sourceware.org \ --cc=hjl.tools@gmail.com \ --cc=indu.bhagat@oracle.com \ --cc=jbeulich@suse.com \ --cc=mengqinggang@loongson.cn \ --cc=nickc@redhat.com \ --cc=saurabh.jha@arm.com \ --cc=simon.marchi@efficios.com \ --cc=srinath.parvathaneni@arm.com \ --cc=tdevries@suse.de \ --cc=tom@tromey.com \ --cc=tromey@adacore.com \ --cc=vapier@gentoo.org \ --cc=victor.donascimento@arm.com \ --cc=vladimir.mezentsev@oracle.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).