Bug fix: Use rundir to determine executable file name in tests

This commit fixes the issue raised in PR #2083 by @lizziel.  Integration
and parallel test execute scripts now use the run directory name and not
the absolute path to determine the executable file name.

test/integration/GCClassic/integrationTestExecute.sh
test/integration/GCHP/integrationTestExecute.sh
test/parallel/GCClassic/parallelTestExecute.sh
- Pass ${runDir} instead of ${runAbsPath} to the exe_name function.
  This will prevent integration test root paths with e.g. "rrtmg"
  from returning an incorrect executable name.

Signed-off-by: Bob Yantosca <yantosca@seas.harvard.edu>

test/integration/GCClassic/integrationTestExecute.sh

@@ -170,7 +170,7 @@ for runDir in *; do
         failMsg="$runDir${FILL:${#runDir}}.....${EXE_FAIL_STR}"
 
         # Get the executable file corresponding to this run directory
-        exeFile=$(exe_name "gcclassic" "${runAbsPath}")
+        exeFile=$(exe_name "gcclassic" "${runDir}")
 
         # Test if the executable exists
         if [[ -f "${binDir}/${exeFile}" ]]; then

test/integration/GCHP/integrationTestExecute.sh

@@ -174,7 +174,7 @@ for runDir in *; do
         failMsg="$runDir${FILL:${#runDir}}.....${EXE_FAIL_STR}"
 
         # Get the executable file corresponding to this run directory
-        exeFile=$(exe_name "gchp" "${runAbsPath}")
+        exeFile=$(exe_name "gchp" "${runDir}")
 
         # Test if the executable exists
         if [[ -f "${binDir}/${exeFile}" ]]; then

test/parallel/GCClassic/parallelTestExecute.sh

@@ -166,7 +166,7 @@ for runDir in *; do
         failMsg="$runDir${FILL:${#runDir}}.....${EXE_FAIL_STR}"
 
         # Get the executable file corresponding to this run directory
-        exeFile=$(exe_name "gcclassic" "${runAbsPath}")
+        exeFile=$(exe_name "gcclassic" "${runDir}")
 
         # Test if the executable exists
         if [[ -f "${binDir}/${exeFile}" ]]; then