From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/6] Fix several cases of unstable test names
Date: Mon, 23 Oct 2017 14:18:00 -0000 [thread overview]
Message-ID: <1508768307-11531-1-git-send-email-palves@redhat.com> (raw)
I frequently diff testresults between builds in different build and
source directories, and that reveals several spurious differences.
Most are caused by the fact the some tests include the source or build
directories in their names, like:
-PASS: gdb.arch/arc-tdesc-cpu.exp: set tdesc filename /home/pedro/gdb1/src/gdb/testsuite/gdb.arch/arc-tdesc-cpu.xml
+PASS: gdb.arch/arc-tdesc-cpu.exp: set tdesc filename /home/pedro/gdb2/src/gdb/testsuite/gdb.arch/arc-tdesc-cpu.xml
^^^^
-PASS: gdb.base/startup-with-shell.exp: touch /home/pedro/gdb1/build/gdb/testsuite/outputs/gdb.base/startup-with-shell/unique-file.unique-extension
+PASS: gdb.base/startup-with-shell.exp: touch /home/pedro/gdb2/build/gdb/testsuite/outputs/gdb.base/startup-with-shell/unique-file.unique-extension
^^^^
(I've underlined the differences above.)
though there are other causes too. See each individual patch.
This series fixes all the spurious differences I see when native
testing on GNU/Linux.
Pedro Alves (6):
Fix unstable test names in gdb.arch/arc-tdesc-cpu.exp
Fix unstable test names in gdb.base/startup-with-shell.exp
Fix unstable test names in gdb.gdb/unittest.exp
Fix unstable test names in gdb.python/py-objfile.exp
Fix unstable test names in gdb.threads/attach-into-signal.exp
Drop /proc/PID/status polling from gdb.threads/attach-into-signal.exp
gdb/testsuite/gdb.arch/arc-tdesc-cpu.exp | 8 +++----
gdb/testsuite/gdb.base/startup-with-shell.exp | 7 ++++--
gdb/testsuite/gdb.gdb/unittest.exp | 3 ++-
gdb/testsuite/gdb.threads/attach-into-signal.exp | 28 ------------------------
gdb/testsuite/lib/gdb-python.exp | 16 +++++++++-----
5 files changed, 21 insertions(+), 41 deletions(-)
--
2.5.5
next reply other threads:[~2017-10-23 14:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 14:18 Pedro Alves [this message]
2017-10-23 14:18 ` [PATCH 1/6] Fix unstable test names in gdb.arch/arc-tdesc-cpu.exp Pedro Alves
2017-10-23 14:18 ` [PATCH 4/6] Fix unstable test names in gdb.python/py-objfile.exp Pedro Alves
2017-10-23 14:18 ` [PATCH 2/6] Fix unstable test names in gdb.base/startup-with-shell.exp Pedro Alves
2017-10-23 16:24 ` Yao Qi
2017-10-24 9:58 ` Pedro Alves
2017-10-23 14:18 ` [PATCH 5/6] Fix unstable test names in gdb.threads/attach-into-signal.exp Pedro Alves
2017-10-23 14:18 ` [PATCH 3/6] Fix unstable test names in gdb.gdb/unittest.exp Pedro Alves
2017-10-23 14:28 ` [PATCH 6/6] Drop /proc/PID/status polling from gdb.threads/attach-into-signal.exp Pedro Alves
2017-10-24 7:27 ` Yao Qi
2017-10-24 10:00 ` [pushed] Reindent gdb.threads/attach-into-signal.exp (Re: [PATCH 6/6] Drop /proc/PID/status polling from gdb.threads/attach-into-signal.exp) Pedro Alves
2017-10-24 10:09 ` [PATCH 7/6] More gdb.threads/attach-into-signal.exp stale stopped bits " Pedro Alves
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=1508768307-11531-1-git-send-email-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@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