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] gdb/testsuite: Make test names unique in gdb.base/watchpoint.exp
Date: Sun, 09 Sep 2018 04:35:00 -0000 [thread overview]
Message-ID: <96b6697fd807428f3832bdab1527ad55156e88d7@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 96b6697fd807428f3832bdab1527ad55156e88d7 ***
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 96b6697fd807428f3832bdab1527ad55156e88d7
gdb/testsuite: Make test names unique in gdb.base/watchpoint.exp
Extend test names and add test name prefixes to make test names
unique.
gdb/testsuite/ChangeLog:
* gdb.base/watchpoint.exp (test_complex_watchpoint): Extend test
names, and add test prefixes to make test names unique.
next reply other threads:[~2018-09-07 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 4:35 sergiodj+buildbot [this message]
2018-09-09 4:35 ` *** COMPILATION FAILED *** Failures on RHEL-s390x-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2018-09-09 4:36 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-09-09 4:59 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-09-09 5:03 ` *** COMPILATION FAILED *** Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-09-09 5:23 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2018-09-09 5:35 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-09-09 5:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-09-09 5:44 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-09-09 6:08 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-09-09 6:21 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-09-11 1:39 ` Failures on Fedora-s390x-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=96b6697fd807428f3832bdab1527ad55156e88d7@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).