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] Remove is_remote target check from gdb.base/dprintf-non-stop.exp
Date: Thu, 12 Oct 2017 19:12:00 -0000 [thread overview]
Message-ID: <8d7aea574a8ab3a235088866860df75b542ae4a3@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 8d7aea574a8ab3a235088866860df75b542ae4a3 ***
Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 8d7aea574a8ab3a235088866860df75b542ae4a3
Remove is_remote target check from gdb.base/dprintf-non-stop.exp
1. is_remote is not the right check.
2. Both Simon & Pedro ran it continuously for some time against
native-gdbserver and didn't see a failure.
3. The test has been running against native-extended-gdbserver anyway.
gdb/testsuite/ChangeLog:
2017-10-12 Simon Marchi <simon.marchi@polymtl.ca>
Pedro Alves <palves@redhat.com>
* gdb.base/dprintf-non-stop.exp: Remove is_remote target check.
next reply other threads:[~2017-10-12 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 19:12 sergiodj+buildbot [this message]
2017-10-12 19:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-10-12 21:16 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-12 21:42 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-10-12 22:07 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-13 6:59 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-10-13 7:38 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-10-13 8:13 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-10-13 8:16 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-10-13 8:31 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-10-13 8:36 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " 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=8d7aea574a8ab3a235088866860df75b542ae4a3@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).