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] Stabilize gdb-caching-proc.exp test order
Date: Wed, 21 Aug 2019 18:06:00 -0000	[thread overview]
Message-ID: <61f80d5dafebdb3a2cebac489803c5ce18827178@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 61f80d5dafebdb3a2cebac489803c5ce18827178 ***

commit 61f80d5dafebdb3a2cebac489803c5ce18827178
Author:     Tom de Vries <tdevries@suse.de>
AuthorDate: Wed Aug 21 11:49:33 2019 +0200
Commit:     Tom de Vries <tdevries@suse.de>
CommitDate: Wed Aug 21 11:49:33 2019 +0200

    [gdb/testsuite] Stabilize gdb-caching-proc.exp test order
    
    The test-case gdb-caching-proc.exp tests each gdb_caching_proc in
    gdb/testsuite/lib/*.exp.  However, the order of .exp file being tested can
    change from run to run, because of using glob.
    
    Fix this by sorting the glob result.
    
    Tested on x86_64-linux.
    
    gdb/testsuite/ChangeLog:
    
    2019-08-21  Tom de Vries  <tdevries@suse.de>
    
            * gdb.base/gdb-caching-proc.exp: Sort files.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 5bc5f77ba0..7fea9cd071 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2019-08-21  Tom de Vries  <tdevries@suse.de>
+
+	* gdb.base/gdb-caching-proc.exp: Sort files.
+
 2019-08-20  Tom de Vries  <tdevries@suse.de>
 
 	* lib/pascal.exp (gdb_compile_pascal): Remove $destfile before
diff --git a/gdb/testsuite/gdb.base/gdb-caching-proc.exp b/gdb/testsuite/gdb.base/gdb-caching-proc.exp
index 82645b0008..ee78727939 100644
--- a/gdb/testsuite/gdb.base/gdb-caching-proc.exp
+++ b/gdb/testsuite/gdb.base/gdb-caching-proc.exp
@@ -104,6 +104,7 @@ if { ![gdb_simple_compile $me $src executable] } {
 
 # Test gdb_caching_procs in gdb/testsuite/lib/*.exp
 set files [eval glob -types f $srcdir/lib/*.exp]
+set files [lsort $files]
 foreach file $files {
     test_file $file
 }


             reply	other threads:[~2019-08-21 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 18:06 gdb-buildbot [this message]
2019-08-21 18:08 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-cc-with-index, branch master *** BREAKAGE *** gdb-buildbot
2019-08-21 18:09 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-08-21 18:16 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot
2019-08-21 18:16 ` *** COMPILATION FAILED *** Failures on Fedora-i686, branch master *** BREAKAGE *** gdb-buildbot
2019-08-21 18:19 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-m64, " gdb-buildbot
2019-08-21 18:22 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-08-21 18:23 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-m32, " gdb-buildbot
2019-08-21 18:36 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-08-21 18:36 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, branch master gdb-buildbot
2019-08-21 18:37 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-gdbserver-m64, branch master *** BREAKAGE *** 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=61f80d5dafebdb3a2cebac489803c5ce18827178@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: 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).