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] Use boards/local-board.exp more
Date: Thu, 30 Nov 2017 17:48:00 -0000 [thread overview]
Message-ID: <f1af7b94c16029f2c6da9eae4076f64cd9383687@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT f1af7b94c16029f2c6da9eae4076f64cd9383687 ***
Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: f1af7b94c16029f2c6da9eae4076f64cd9383687
Use boards/local-board.exp more
local-board.exp was introduced recently, containing the code required to
force the gdbserver boards to be non-remote (from the DejaGNU point of
view). Other board files use the same trick of forcing isremote to 0.
Instead of doing it by hand in each file, include local-board.exp.
gdb/testsuite/ChangeLog:
* boards/cc-with-tweaks.exp: Include local-board.exp instead of
setting isremote by hand.
* boards/dwarf4-gdb-index.exp: Likewise.
* boards/fission.exp: Likewise.
* boards/stabs.exp: Likewise.
next reply other threads:[~2017-11-30 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 17:48 sergiodj+buildbot [this message]
2017-11-30 17:48 ` Failures on Fedora-x86_64-cc-with-index, branch master sergiodj+buildbot
2017-11-30 17:54 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-30 18:07 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-11-30 18:08 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-11-30 18:09 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-11-30 18:41 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-12-01 4:37 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-12-01 5:04 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-12-01 5:29 ` Failures on Ubuntu-AArch32-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=f1af7b94c16029f2c6da9eae4076f64cd9383687@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).