About the Execution
Execution Summary | ||||
Max Memory Used (MB) |
CPU Usage (ms) | I/O Wait (ms) | Competition Result | Execution Status |
421.07 | 3000875 | 10 | __________ | normal |
Execution Chart
We display below the execution chart for this examination (boot time has been removed).
Trace from the execution
Waiting for the VM to be ready (probing ssh)
..................
=====================================================================
Generated by BenchKit 2-1667
Executing tool lola
Input is Dekker-PT-200, examination is ReachabilityFireabilitySimple
Time confinement is 3600 seconds
Memory confinement is 6144 MBytes
Run identifier is r01kn-qhx2-140025666201397
=====================================================================
--------------------
content from stdout:
BK_START 1401860002668
make: Nothing to be done for `prepare'.
ReachabilityFireabilitySimple @ execution
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-1 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-10 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-2 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-3 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-4 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-5 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-6 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-7 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-8 CANNOT_COMPUTE
FORMULA Dekker-PT-200-ReachabilityFireabilitySimple-9 CANNOT_COMPUTE
BK_STOP 1401863010173
--------------------
content from stderr:
make: [verify] Error 3 (ignored)
Sequence of Actions to be Executed by the VM
This is useful if one wants to reexecute the tool in the VM from the submitted image disk.
set -x
# this is for BenchKit: configuration of major elements for the test
export BK_INPUT="Dekker-PT-200"
export BK_EXAMINATION="ReachabilityFireabilitySimple"
export BK_TOOL="lola"
export BK_RESULT_DIR="/home/fko/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="3600"
# this is specific to your benchmark or test
export BIN_DIR="$HOME/BenchKit/bin"
# remove the execution directoty if it exists (to avoid increse of .vmdk images)
if [ -d execution ] ; then
rm -rf execution
fi
tar xzf /home/mcc/BenchKit/INPUTS/Dekker-PT-200.tgz
mv Dekker-PT-200 execution
# this is for BenchKit: explicit launching of the test
cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-1667"
echo " Executing tool lola"
echo " Input is Dekker-PT-200, examination is ReachabilityFireabilitySimple"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 6144 MBytes"
echo " Run identifier is r01kn-qhx2-140025666201397"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo -n "BK_START "
date -u +%s%3N
timeout -s 9 $BK_TIME_CONFINEMENT bash -c "/home/mcc/BenchKit/BenchKit_head.sh 2> STDERR ; echo ; echo -n \"BK_STOP \" ; date -u +%s%3N"
if [ $? -eq 137 ] ; then
echo
echo "BK_TIME_CONFINEMENT_REACHED"
fi
echo
echo "--------------------"
echo "content from stderr:"
echo
cat STDERR ;