- ABT_JOBS: allows parallel builds -- it's passed as the argument to
"make -j" when building Valgrind and the tests. The default is 1.
+ - ABT_PERF: unset or set to "" mean 'do not run perf tests' (default value)
+ set to "--vg=../valgrind-new" (run perf tests for new tree)
+ set to "--vg=../valgrind-new --vg=../valgrind-old"
+ (run perf tests for "new" and for "24 hours ago",
+ to compare the performances between the 2 trees).
+
+ - ABT_PERF_TOOLS: --tools=.... option of perf/vg_perf.
+ (default value: all non experimental tools)
+
+ - ABT_PERF_REPS: --reps=... option of perf/vg_perf
+ (default value: --reps=3)
+
Note that the appropriate syntax to use in this file will depend on the
shell from which the $DIR/bin/nightly script is run (which in turn may
depend on what shell is used by cron or any similar program).
ABT_RUN_REGTEST="make regtest"
fi
+if [ "${ABT_PERF_TOOLS}" = "" ]; then
+ ABT_PERF_TOOLS="--tools=none,memcheck,callgrind,helgrind,cachegrind,drd,massif"
+fi
+if [ "${ABT_PERF_REPS}" = "" ]; then
+ ABT_PERF_REPS="--reps=3"
+fi
+
#----------------------------------------------------------------------------
# Check out, build, test
)
done
+# if requested, run regression tests and produce results in perflogfile.out
+if [ "${ABT_PERF}" != "" ]; then
+ cd valgrind-new
+ echo ${ABT_PERF_TOOLS} ${ABT_PERF_REPS} ${ABT_PERF} > ../perflogfile
+ (time perl perf/vg_perf ${ABT_PERF_TOOLS} ${ABT_PERF_REPS} ${ABT_PERF} perf) >> ../perflogfile 2>&1
+ cd ..
+fi
+
+
#----------------------------------------------------------------------------
# Prepare results and send
#----------------------------------------------------------------------------
echo >> final
fi
+# add perf results if requested
+if [ "${ABT_PERF}" != "" ]; then
+ cat perflogfile >> final
+fi
+
# Gather up the diffs (at most the first 100 lines for each one) into a
# single file.
MAX_LINES=100