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] Fix duplicate test message in mi-trace-save.exp
Date: Mon, 17 Oct 2016 23:24:00 -0000 [thread overview]
Message-ID: <e42b25a0407fbbf3529815f69bd56a61b1821295@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT e42b25a0407fbbf3529815f69bd56a61b1821295 ***
Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: e42b25a0407fbbf3529815f69bd56a61b1821295
Fix duplicate test message in mi-trace-save.exp
gdb/testsuite/ChangeLog:
* gdb.trace/mi-trace-save.exp (test_trace_save_wrong_num_args):
Change test message.
next reply other threads:[~2016-10-17 23:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 23:24 sergiodj+buildbot [this message]
2016-10-17 23:24 ` Failures on Ubuntu-AArch64-m64, branch master sergiodj+buildbot
2016-10-17 23:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-10-17 23:47 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-10-18 0:10 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-10-18 0:13 ` Failures on Debian-i686, " sergiodj+buildbot
2016-10-18 0:18 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2016-10-18 0:48 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-10-18 4:54 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-10-18 8:17 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-10-18 9:08 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-10-18 9:41 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-10-18 11:16 ` Failures on Fedora-ppc64le-native-extended-gdbserver-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=e42b25a0407fbbf3529815f69bd56a61b1821295@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).