About the Execution of ydd-pt for TokenRing-PT-040
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
573.810 | 16.00 | 3040.00 | 0.00 | [undef] | Cannot compute |
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-2979
Executing tool yddpt
Input is TokenRing-PT-040, examination is UpperBounds
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r144kn-smll-146384410800137
=====================================================================
--------------------
content from stdout:
=== Data for post analysis generated by BenchKit (invocation template)
The expected result is a vector of positive values
NUM_VECTOR
here is the order used to build the result vector(from text file)
FORMULA_NAME TokenRing-COL-040-UpperBounds-0
FORMULA_NAME TokenRing-COL-040-UpperBounds-1
FORMULA_NAME TokenRing-COL-040-UpperBounds-10
FORMULA_NAME TokenRing-COL-040-UpperBounds-11
FORMULA_NAME TokenRing-COL-040-UpperBounds-12
FORMULA_NAME TokenRing-COL-040-UpperBounds-13
FORMULA_NAME TokenRing-COL-040-UpperBounds-14
FORMULA_NAME TokenRing-COL-040-UpperBounds-15
FORMULA_NAME TokenRing-COL-040-UpperBounds-2
FORMULA_NAME TokenRing-COL-040-UpperBounds-3
FORMULA_NAME TokenRing-COL-040-UpperBounds-4
FORMULA_NAME TokenRing-COL-040-UpperBounds-5
FORMULA_NAME TokenRing-COL-040-UpperBounds-6
FORMULA_NAME TokenRing-COL-040-UpperBounds-7
FORMULA_NAME TokenRing-COL-040-UpperBounds-8
FORMULA_NAME TokenRing-COL-040-UpperBounds-9
=== Now, execution of the tool begins
BK_START 1463912211909
BK_STOP 1463912211925
--------------------
content from stderr:
/home/mcc/BenchKit/BenchKit_head.sh: line 38: $BK_LOG_FILE: ambiguous redirect
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="TokenRing-PT-040"
export BK_EXAMINATION="UpperBounds"
export BK_TOOL="yddpt"
export BK_RESULT_DIR="/root/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="3600"
export BK_MEMORY_CONFINEMENT="16384"
# 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/TokenRing-PT-040.tgz
mv TokenRing-PT-040 execution
# this is for BenchKit: explicit launching of the test
cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-2979"
echo " Executing tool yddpt"
echo " Input is TokenRing-PT-040, examination is UpperBounds"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r144kn-smll-146384410800137"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "UpperBounds" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "UpperBounds" != "StateSpace" ] ; then
echo "The expected result is a vector of booleans"
echo BOOL_VECTOR
else
echo "no data necessary for post analysis"
fi
echo
if [ -f "UpperBounds.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property UpperBounds.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "UpperBounds.xml" ] ; then # for cunf (txt files deleted;-)
echo echo "here is the order used to build the result vector(from xml file)"
for x in $(grep '
echo "FORMULA_NAME $x"
done
fi
echo
echo "=== Now, execution of the tool begins"
echo
echo -n "BK_START "
date -u +%s%3N
echo
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 ;