public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Make dprintf-non-stop.exp cope with remote testing
Date: Mon, 30 Nov 2015 21:07:00 -0000 [thread overview]
Message-ID: <09df4675f2e4f8f098954f9a38f44d12089f1c4e@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 09df4675f2e4f8f098954f9a38f44d12089f1c4e ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 09df4675f2e4f8f098954f9a38f44d12089f1c4e
Make dprintf-non-stop.exp cope with remote testing
Testing with the extended-remote board with "maint set target-non-stop
on" shows a dprintf-non-stop.exp regression. The issue is simply that
the test is expecting output that is only valid for the native target:
native:
[process 8676] #1 stopped.
remote:
[Thread 8900.8900] #1 stopped.
In order to expose this without "maint set target-non-stop on", this
restarts gdb with non-stop mode already enabled.
gdb/testsuite/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* gdb.base/dprintf-non-stop.exp: Use build_executable instead of
prepare_for_testing. Start gdb with "set non-stop on" appended to
GDBFLAGS. Lax expected stop output.
next reply other threads:[~2015-11-30 21:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 21:07 sergiodj+buildbot [this message]
2015-11-30 21:07 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2015-11-30 23:25 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2015-11-30 23:39 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2015-11-30 23:43 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-01 1:14 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2015-12-01 2:53 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2015-12-01 5:46 ` Failures on Debian-i686, " sergiodj+buildbot
2015-12-01 6:06 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-12-01 6:29 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-12-01 14:14 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2015-12-01 14:23 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-12-01 14:29 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2015-12-01 14:31 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-12-01 14:36 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-08 11:42 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-12-08 11:57 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2015-12-08 12:19 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-12-08 12:39 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-09 5:41 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-09 5:58 ` Failures on Fedora-ppc64le-native-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=09df4675f2e4f8f098954f9a38f44d12089f1c4e@gdb-build \
--to=sergiodj+buildbot@redhat.com \
--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).