public inbox for gdbadmin@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: "Aaron Merey" <amerey@redhat.com>, "Alan Modra" <amodra@gmail.com>, "Andrew Burgess" <aburgess@redhat.com>, "GDB Administrator" <gdbadmin@sourceware.org>, "H.J. Lu" <hjl.tools@gmail.com>, "Jan Beulich" <jbeulich@suse.com>, "John Baldwin" <jhb@FreeBSD.org>, "Mark Wielaard" <mark@klomp.org>, "Martin Liska" <mliska@suse.cz>, "Nick Clifton" <nickc@redhat.com>, "Pedro Alves" <pedro@palves.net>, "Simon Marchi" <simon.marchi@efficios.com>, "Simon Marchi" <simon.marchi@polymtl.ca>, "Stefan Liebler" <stli@linux.ibm.com>, "Thomas Hebb" <tommyhebb@gmail.com>, "Tom Tromey" <tom@tromey.com>, "Tom Tromey" <tromey@adacore.com>, "Tom de Vries" <tdevries@suse.de>, "Vladimir Mezentsev" <vladimir.mezentsev@oracle.com> Cc: gdb-testers@sourceware.org Subject: ☺ Buildbot (GNU Toolchain): binutils-gdb - build successful (master) Date: Wed, 04 May 2022 14:42:20 +0000 [thread overview] Message-ID: <20220504144220.4A811385E03D@sourceware.org> (raw) A restored build has been detected on builder gdb-fedora-s390x while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/75/builds/86 Build state: build successful Revision: 716e54731f30bc60b2fc52996ebe4fc087420b2e Worker: fedora-s390x Build Reason: (unknown) Blamelist: Aaron Merey <amerey@redhat.com>, Alan Modra <amodra@gmail.com>, Andrew Burgess <aburgess@redhat.com>, GDB Administrator <gdbadmin@sourceware.org>, H.J. Lu <hjl.tools@gmail.com>, Jan Beulich <jbeulich@suse.com>, John Baldwin <jhb@FreeBSD.org>, Mark Wielaard <mark@klomp.org>, Martin Liska <mliska@suse.cz>, Nick Clifton <nickc@redhat.com>, Pedro Alves <pedro@palves.net>, Simon Marchi <simon.marchi@efficios.com>, Simon Marchi <simon.marchi@polymtl.ca>, Stefan Liebler <stli@linux.ibm.com>, Thomas Hebb <tommyhebb@gmail.com>, Tom Tromey <tom@tromey.com>, Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>, Vladimir Mezentsev <vladimir.mezentsev@oracle.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/75/builds/86/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/75/builds/86/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/75/builds/86/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/75/builds/86/steps/4/logs/stdio - warnings (14): https://builder.sourceware.org/buildbot/#builders/75/builds/86/steps/4/logs/warnings__14_
next reply other threads:[~2022-05-04 14:42 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-04 14:42 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-05-04 4:46 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=20220504144220.4A811385E03D@sourceware.org \ --to=builder@sourceware.org \ --cc=aburgess@redhat.com \ --cc=amerey@redhat.com \ --cc=amodra@gmail.com \ --cc=gdb-testers@sourceware.org \ --cc=gdbadmin@sourceware.org \ --cc=hjl.tools@gmail.com \ --cc=jbeulich@suse.com \ --cc=jhb@FreeBSD.org \ --cc=mark@klomp.org \ --cc=mliska@suse.cz \ --cc=nickc@redhat.com \ --cc=pedro@palves.net \ --cc=simon.marchi@efficios.com \ --cc=simon.marchi@polymtl.ca \ --cc=stli@linux.ibm.com \ --cc=tdevries@suse.de \ --cc=tom@tromey.com \ --cc=tommyhebb@gmail.com \ --cc=tromey@adacore.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).