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] sim: d10v: link in missing testsuite
Date: Mon, 30 Mar 2015 10:29:00 -0000 [thread overview]
Message-ID: <e8713c0f026199c327ba88ea6da4bcffebff6991@kwanyin> (raw)
*** TEST RESULTS FOR COMMIT e8713c0f026199c327ba88ea6da4bcffebff6991 ***
Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: e8713c0f026199c327ba88ea6da4bcffebff6991
sim: d10v: link in missing testsuite
Looks like historical restructuring in this dir lost the d10v-elf subdir
and no one noticed in the meantime. Re-add it to the testsuite.
There are some failures, but better some tests get run than none at all.
next reply other threads:[~2015-03-30 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 10:29 sergiodj+buildbot [this message]
2015-03-30 10:41 ` Failures on Fedora-ppc64be-cc-with-index, branch master sergiodj+buildbot
2015-03-30 11:23 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-03-30 12:08 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-03-30 18:48 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2015-03-30 19:10 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-03-31 4:23 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-03-31 4:50 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-03-31 5:04 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2015-04-02 0:39 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-04-02 1:14 ` Failures on Fedora-x86_64-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=e8713c0f026199c327ba88ea6da4bcffebff6991@kwanyin \
--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).