summaryrefslogtreecommitdiffstats
path: root/test/testcheck_version.sh.in
diff options
context:
space:
mode:
authorAlbert Cheng <acheng@hdfgroup.org>2009-11-04 22:08:49 (GMT)
committerAlbert Cheng <acheng@hdfgroup.org>2009-11-04 22:08:49 (GMT)
commita81d1b40351c85129b2202bf504e4daed59813d8 (patch)
treeaf326b38ce9308ebb0ccf86e9e6535a80b25eaf5 /test/testcheck_version.sh.in
parent9e170a0be0d65da756516734ab1db780871cf9f7 (diff)
downloadhdf5-a81d1b40351c85129b2202bf504e4daed59813d8.zip
hdf5-a81d1b40351c85129b2202bf504e4daed59813d8.tar.gz
hdf5-a81d1b40351c85129b2202bf504e4daed59813d8.tar.bz2
[svn-r17832] Bug fix:(sort of)
Some systems, like AIX poe, interpret exit(134) the same as if the process has really been interrupted by the abort signal and prints extra messages that confuse test script which is looking for matching output. Solution: Changed it to exit(6) which still has the "appearance" of an abort signal which carries the value of 6 in Unix systems. Tested: LLNL Up both serial and Parallel.
Diffstat (limited to 'test/testcheck_version.sh.in')
-rw-r--r--test/testcheck_version.sh.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/testcheck_version.sh.in b/test/testcheck_version.sh.in
index e2fa44c..6e80654 100644
--- a/test/testcheck_version.sh.in
+++ b/test/testcheck_version.sh.in
@@ -162,7 +162,7 @@ TESTING() {
;;
*) # W/A: Warning, abort and exit non-0.
WarnMesg > $expect
- expect_code=134 # Signal Abort exit code (128+6)
+ expect_code=6 # Signal Abort exit code (128+6)
;;
esac
fi