public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb/gdb-8.1-branch] Set GDB version number to 8.1.1.
Date: Tue, 31 Jul 2018 15:37:00 -0000 [thread overview]
Message-ID: <f99d9b9f436dce02aa06839395c67d400b2a0de0@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT f99d9b9f436dce02aa06839395c67d400b2a0de0 ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.1-branch
Commit: f99d9b9f436dce02aa06839395c67d400b2a0de0
Set GDB version number to 8.1.1.
gdb/ChangeLog:
* version.in: Set GDB version number to 8.1.1.
* PROBLEMS: Likewise.
next reply other threads:[~2018-07-31 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 15:37 sergiodj+buildbot [this message]
2018-07-31 15:37 ` Failures on RHEL-s390x-m64, branch gdb-8.1-branch sergiodj+buildbot
2018-07-31 19:48 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-07-31 20:03 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-07-31 20:11 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-07-31 20:11 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch gdb-8.1-branch *** BREAKAGE *** sergiodj+buildbot
2018-07-31 20:12 ` Failures on Fedora-i686, branch gdb-8.1-branch sergiodj+buildbot
2018-07-31 20:24 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-07-31 20:26 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-07-31 20:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-07-31 20:59 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-07-31 21:16 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-07-31 21:51 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-08-18 16:16 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-08-31 19:09 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
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=f99d9b9f436dce02aa06839395c67d400b2a0de0@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--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: link
Be 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).