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 Python test to use lowercase command
Date: Sat, 11 Feb 2017 02:51:00 -0000	[thread overview]
Message-ID: <b964bee0f058b8e63c9206a8862b2fc1253f1bbd@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT b964bee0f058b8e63c9206a8862b2fc1253f1bbd ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: b964bee0f058b8e63c9206a8862b2fc1253f1bbd

Fix Python test to use lowercase command

While testing this series I saw some errors from the Python test
suite.  There were a couple of tests using "P" as a command; this
changes them to "p".

gdb/testsuite/ChangeLog
2017-02-10  Tom Tromey  <tom@tromey.com>

	* gdb.python/py-xmethods.exp: Use "p" command, not "P".


             reply	other threads:[~2017-02-11  2:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11  2:51 sergiodj+buildbot [this message]
2017-02-11  2:51 ` Failures on Debian-s390x-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2017-02-11  3:28 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-02-11  3:35 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2017-02-11  4:26 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-02-11  4:48 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-02-12  0:18 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2017-02-12  1:09 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-02-12  4:11 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2017-02-12  6:27 ` 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=b964bee0f058b8e63c9206a8862b2fc1253f1bbd@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).