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] Run gdb.base/catch-fork-static.exp on remote target boards
Date: Fri, 13 Oct 2017 00:06:00 -0000 [thread overview]
Message-ID: <6bf0052db8bbeed41e512d1d3ce14ba2a446723d@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 6bf0052db8bbeed41e512d1d3ce14ba2a446723d ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6bf0052db8bbeed41e512d1d3ce14ba2a446723d
Run gdb.base/catch-fork-static.exp on remote target boards
Another case of a stale check. We support following forks in the
remote protocol nowadays.
gdb/testsuite/ChangeLog:
2017-10-12 Pedro Alves <palves@redhat.com>
Simon Marchi <simon.marchi@polymtl.ca>
* gdb.base/catch-fork-static.exp: No longer skip on is_remote
target boards.
next reply other threads:[~2017-10-13 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 0:06 sergiodj+buildbot [this message]
2017-10-13 0:06 ` Failures on Ubuntu-AArch32-m32, branch master sergiodj+buildbot
2017-10-13 0:30 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-13 0:55 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-13 1:19 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-13 10:37 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-13 10:39 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-10-13 10:56 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-10-13 11:28 ` 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=6bf0052db8bbeed41e512d1d3ce14ba2a446723d@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).