public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/testsuite: Disable path and duplicate checks when parallel testing Date: Tue, 12 May 2020 16:44:25 +0000 (GMT) [thread overview] Message-ID: <20200512164425.B9F30387085C@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=843f4d93576eef02139f7b1b3fa1cea7b0f286f1 commit 843f4d93576eef02139f7b1b3fa1cea7b0f286f1 Author: Andrew Burgess <andrew.burgess@embecosm.com> Date: Tue May 12 17:38:17 2020 +0100 gdb/testsuite: Disable path and duplicate checks when parallel testing This commit disables the recently added checking for paths in test names, and for duplicate test names, when the gdb tests are run in parallel. When running the gdb tests in parallel the extra result count lines produced cause the dg-extract-results scripts to exit with an error. The patches for the dg-extract-results scripts have been posted to the gcc-patches mailing list here: https://gcc.gnu.org/pipermail/gcc-patches/2020-May/545562.html Once they are merged there then these changes can be merged over to binutils-gdb, and this commit can be reverted. gdb/testsuite/ChangeLog: * lib/check-test-names.exp: Disable when testing is being run in parallel. Diff: --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/lib/check-test-names.exp | 20 ++++++++++++++++++++ 2 files changed, 25 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index cd8440d35e0..98cff469033 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2020-05-12 Andrew Burgess <andrew.burgess@embecosm.com> + + * lib/check-test-names.exp: Disable when testing is being run in + parallel. + 2020-05-12 Tom de Vries <tdevries@suse.de> * gdb.base/jit-elf.exp: Fix string concat. diff --git a/gdb/testsuite/lib/check-test-names.exp b/gdb/testsuite/lib/check-test-names.exp index 4c0fde6e4ea..79139adea7a 100644 --- a/gdb/testsuite/lib/check-test-names.exp +++ b/gdb/testsuite/lib/check-test-names.exp @@ -18,6 +18,26 @@ # name. When a test includes the path in its test name it is harder # to compare results between two runs of GDB from different trees. +# This is a short term hack (12-May-2020). If we are running tests in +# parallel then we need support in the contrib/dg-extract-results.* +# scripts to merge the new result types generated by this file back +# into the single unified summary file. If this support is not in +# place then the dg-extract-results script will exit with an error. +# +# The script changes need to first be merged into the gcc repository, +# then copied over to the binutils-gdb repository. The required +# changes have been posted to the gcc list here: +# +# https://gcc.gnu.org/pipermail/gcc-patches/2020-May/545562.html +# +# But until these are merged into binutils-gdb the extra checks +# offered by this file can only be done when the tests are not running +# in parallel. +if {[info exists GDB_PARALLEL]} { + # Don't load this file. + return +} + namespace eval ::CheckTestNames { # An associative array of all test names to the number of times each # name is seen. Used to detect duplicate test names.
reply other threads:[~2020-05-12 16:44 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200512164425.B9F30387085C@sourceware.org \ --to=aburgess@sourceware.org \ --cc=gdb-cvs@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).