public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] gdb/testsuite: Remove paths and make test names unique Date: Mon, 23 Mar 2020 20:20:36 -0400 [thread overview] Message-ID: <1b83d09cd503d7fde57c50db51d5780ee8df5fae@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 1b83d09cd503d7fde57c50db51d5780ee8df5fae *** commit 1b83d09cd503d7fde57c50db51d5780ee8df5fae Author: Andrew Burgess <andrew.burgess@embecosm.com> AuthorDate: Fri Mar 13 23:28:46 2020 +0000 Commit: Andrew Burgess <andrew.burgess@embecosm.com> CommitDate: Fri Mar 13 23:35:23 2020 +0000 gdb/testsuite: Remove paths and make test names unique Removes paths from some test names, and make the test names unique in the gdb.base/break-interp.exp test file. gdb/testsuite/ChangeLog: * gdb.base/break-interp.exp: Use the tail of the filename, not the full path in the test name. (test_ld): Add some with_test_prefix blocks to make test names unique. diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 48d3c94685..500aa51c34 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,10 @@ +2020-03-13 Andrew Burgess <andrew.burgess@embecosm.com> + + * gdb.base/break-interp.exp: Use the tail of the filename, not the + full path in the test name. + (test_ld): Add some with_test_prefix blocks to make test names + unique. + 2020-03-13 Tom de Vries <tdevries@suse.de> * gdb.mi/mi-sym-info.exp: Fix buffer full errors, and timeouts. diff --git a/gdb/testsuite/gdb.base/break-interp.exp b/gdb/testsuite/gdb.base/break-interp.exp index 3646a1a413..6b03c59c81 100644 --- a/gdb/testsuite/gdb.base/break-interp.exp +++ b/gdb/testsuite/gdb.base/break-interp.exp @@ -411,18 +411,22 @@ proc test_ld {file ifmain trynosym displacement} { reach $solib_bp "run" $displacement 1 - gdb_test_no_output "set verbose off" - gdb_test "bt" "#0 +\[^\r\n\]*\\m(__GI_)?$solib_bp\\M.*" "dl bt" - gdb_test_no_output "set verbose on" + with_test_prefix "first backtrace" { + gdb_test_no_output "set verbose off" + gdb_test "bt" "#0 +\[^\r\n\]*\\m(__GI_)?$solib_bp\\M.*" "dl bt" + gdb_test_no_output "set verbose on" + } if $ifmain { reach "main" continue "NONE" reach "libfunc" continue "NONE" - gdb_test_no_output "set verbose off" - gdb_test "bt" "#0 +\[^\r\n\]*\\mlibfunc\\M\[^\r\n\]*\r\n#1 +\[^\r\n\]*\\mmain\\M.*" "main bt" - gdb_test_no_output "set verbose on" + with_test_prefix "second backtrace" { + gdb_test_no_output "set verbose off" + gdb_test "bt" "#0 +\[^\r\n\]*\\mlibfunc\\M\[^\r\n\]*\r\n#1 +\[^\r\n\]*\\mmain\\M.*" "main bt" + gdb_test_no_output "set verbose on" + } } # Try re-run if the new PIE displacement takes effect. @@ -609,7 +613,7 @@ foreach_with_prefix ldprelink {NO YES} { file delete "${interp}.debug" } - if ![prelink$ldprelink $interp "$interp, second time"] { + if ![prelink$ldprelink $interp "[file tail $interp], second time"] { continue }
next reply other threads:[~2020-03-24 0:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-24 0:20 gdb-buildbot [this message] 2020-03-24 0:20 ` Failures on Fedora-x86_64-cc-with-index, branch master gdb-buildbot 2020-03-24 0:27 ` Failures on Fedora-i686, " gdb-buildbot 2020-03-24 1:12 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2020-03-24 1:29 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2020-03-24 2:09 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2020-03-26 22:16 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot 2020-03-27 7:31 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot 2020-03-27 10:58 ` Failures on Ubuntu-Aarch64-m64, " gdb-buildbot 2020-03-27 11:20 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-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=1b83d09cd503d7fde57c50db51d5780ee8df5fae@gdb-build \ --to=gdb-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: linkBe 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).