parsec: test.sh with many raw run commands

README.adoc

@@ -1883,9 +1883,11 @@ which teaches you that you can run `fmm` as:
 
 ....
 cd /parsec/ext/splash2x/apps/fmm/run
-/parsec/ext/splash2x/apps/fmm/inst/arm-linux.gcc/bin/fmm 1 < input_1
+../inst/arm-linux.gcc/bin/fmm 1 < input_1
 ....
 
+We are also collecting more raw commands for testing at: link:parsec-benchmark/test.sh[]
+
 And so inside of `gem5`, you likely want to do:
 
 ....

parsec-benchmark/external.mk

@@ -40,6 +40,8 @@ define PARSEC_BENCHMARK_INSTALL_TARGET_CMDS
   # know if this works until time consuming testing is done :-)
   mkdir -p '$(TARGET_DIR)/parsec/'
 
+  $(INSTALL) -D -m 0755 '$(PARSEC_BENCHMARK_PKGDIR)/test.sh' '$(TARGET_DIR)/parsec/'
+
   rsync -am $(if $(filter $(V),1),-v,) --include '*/' \
     --include '/bin/***' \
     --include '/config/***' \

parsec-benchmark/test.sh

@@ -0,0 +1,24 @@
+#!/bin/sh
+
+# Since Parsec does not stop on errors and we need some raw commands for gem5,
+# let's do some of our own unit tests here. Thses should be run on QEMU
+# to be reasonably fast.
+
+set -ex
+
+ncpus=1
+
+cd /parsec/ext/splash2x/apps/fmm/run
+../inst/*/bin/fmm "$ncpus" < input_1
+
+cd /parsec/ext/splash2x/apps/raytrace/run
+../inst/*/bin/raytrace -s -p"$ncpus" -a4 teapot.env
+
+cd /parsec/ext/splash2x/apps/volrend/run
+../inst/*/bin/volrend "$ncpus" head-scaleddown4 4 < input_1
+
+cd /parsec/ext/splash2x/apps/water_nsquared/run
+../inst/*/bin/water_nsquared "$ncpus" < input_1
+
+cd /parsec/ext/splash2x/apps/water_spatial/run
+../inst/*/bin/water_spatial "$ncpus" < input_1