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] Add intro comment to length_cond.exp
Date: Wed, 19 Jun 2019 15:59:00 -0000 [thread overview]
Message-ID: <899277ae529c2b743d22093fcc1a9e46aff4422a@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 899277ae529c2b743d22093fcc1a9e46aff4422a ***
Author: Tom Tromey <tromey@adacore.com>
Branch: master
Commit: 899277ae529c2b743d22093fcc1a9e46aff4422a
Add intro comment to length_cond.exp
Pedro pointed out that the new length_cond.exp test did not have an
intro comment. This adds one.
gdb/testsuite/ChangeLog
2019-06-19 Tom Tromey <tromey@adacore.com>
* gdb.ada/length_cond.exp: Add intro comment.
next reply other threads:[~2019-06-19 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 15:59 sergiodj+buildbot [this message]
2019-06-19 16:02 ` *** COMPILATION FAILED *** Failures on RHEL-s390x-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2019-06-19 16:20 ` *** COMPILATION FAILED *** Failures on NetBSD-x86_64-m64, " sergiodj+buildbot
2019-06-19 16:23 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2019-06-19 16:29 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2019-06-19 16:47 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2019-06-19 16:56 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2019-06-19 16:58 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-06-19 17:10 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2019-06-19 17:15 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-06-19 17:15 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2019-06-19 17:22 ` Failures on Fedora-i686, " 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=899277ae529c2b743d22093fcc1a9e46aff4422a@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).