path: root/
diff options
authorJeff Darcy <>2016-04-14 08:49:35 -0400
committerJeff Darcy <>2016-04-15 04:11:18 -0700
commit435e25d510ed74dd9b59b22dcb062daca088327f (patch)
tree7d0457070bffd7ca2c6b044fbf00327abaf83a97 /
parent2b7ae34eff4ed00f15661cf1ca5b2ee07a1d93bd (diff)
tests: fix per-test core detection
This is a backport of the following patch: Commit 9933c5ab in glusterfs-patch-acceptance-tests broke the code here to count cores after each test, with two bad effects: * Tests continue to run after the job is already guaranteed to fail, tying up resources and delaying jobs for other patches. * Cores aren't detected until the end of the job, long after it might have been possible to figure out what was going on at the time the process died. The current check here works for the current code in the other repo, but could break if the two repos are changed without coordination again. Change-Id: I0840849f5df8b6a62893bad1b80b6ace208ffe90 Signed-off-by: Jeff Darcy <> Reviewed-on: Smoke: Gluster Build System <> NetBSD-regression: NetBSD Build System <> CentOS-regression: Gluster Build System <> Reviewed-by: Atin Mukherjee <>
Diffstat (limited to '')
1 files changed, 2 insertions, 2 deletions
diff --git a/ b/
index 7352089..9abe0be 100755
--- a/
+++ b/
@@ -207,7 +207,7 @@ function run_tests()
for t in $(find ${regression_testsdir}/tests -name '*.t' \
| LC_COLLATE=C sort) ; do
- old_cores=$(ls /core.* 2> /dev/null | wc -l)
+ old_cores=$(ls /*-*.core 2> /dev/null | wc -l)
if match $t "$@" ; then
echo "=================================================="
@@ -244,7 +244,7 @@ function run_tests()
- new_cores=$(ls /core.* 2> /dev/null | wc -l)
+ new_cores=$(ls /*-*.core 2> /dev/null | wc -l)
if [ x"$new_cores" != x"$old_cores" ]; then
echo "$t: $core_diff new core files"