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-2270
Executing tool classicMC
Input is S_Dekker-PT-100, examination is ReachabilityBounds
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 4
Run identifier is r127st-blw3-143297563600060
=====================================================================

--------------------
content from stdout:

=== Data for post analysis generated by BenchKit (invocation template)

The expected result is a vector of booleans
BOOL_VECTOR

here is the order used to build the result vector(from text file)
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-0
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-1
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-10
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-11
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-12
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-13
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-14
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-15
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-2
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-3
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-4
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-5
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-6
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-7
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-8
FORMULA_NAME Dekker-PT-100-ReachabilityBounds-9

=== Now, execution of the tool begins

BK_START 1433028191667

---> classicMC --- TAPAAL Classic Multicore

***********************************************
TAPAAL classicMC verifying ReachabilityBounds
***********************************************
Dekker-PT-100-ReachabilityBounds-0: place-bound EF ( true and ("p1_80" < 0 ) and ("flag_0_61" < 0 ) and ("flag_1_21" < 0 ) and ("flag_0_15" < 0 ) and ("flag_1_94" < 0 ) and ("p3_3" < 0 ) and ("p1_7" < 0 ) and ("flag_1_0" < 0 ) and ("p1_72" < 0 ) and ("flag_1_27" < 0 ) and ("flag_1_13" < 0 ) )
Dekker-PT-100-ReachabilityBounds-1: place-bound EF ( true and ("flag_0_81" < 0 ) and ("flag_1_60" < 0 ) and ("p3_6" < 0 ) and ("p1_22" < 0 ) )
Dekker-PT-100-ReachabilityBounds-2: place-bound EF ( true and ("flag_1_3" < 0 ) )
Dekker-PT-100-ReachabilityBounds-3: place-bound EF ( true and ("flag_1_29" < 0 ) )
Dekker-PT-100-ReachabilityBounds-4: place-bound EF ( true and ("p3_15" < 0 ) )
Dekker-PT-100-ReachabilityBounds-5: place-bound EF ( true and ("p0_5" < 0 ) )
Dekker-PT-100-ReachabilityBounds-6: place-bound EF ( true and ("p1_35" < 0 ) )
Dekker-PT-100-ReachabilityBounds-7: place-bound EF ( true and ("p0_23" < 0 ) )
Dekker-PT-100-ReachabilityBounds-8: place-bound EF ( true and ("p1_14" < 0 ) )
Dekker-PT-100-ReachabilityBounds-9: place-bound EF ( true and ("p1_39" < 0 ) and ("p1_22" < 0 ) )
Dekker-PT-100-ReachabilityBounds-10: place-bound EF ( true and ("flag_0_1" < 0 ) and ("p0_41" < 0 ) )
Dekker-PT-100-ReachabilityBounds-11: place-bound EF ( true and ("p0_44" < 0 ) )

BK_TIME_CONFINEMENT_REACHED

--------------------
content from stderr:

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="S_Dekker-PT-100"
export BK_EXAMINATION="ReachabilityBounds"
export BK_TOOL="classicMC"
export BK_RESULT_DIR="/user/u8/hulinhub/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/S_Dekker-PT-100.tgz
mv S_Dekker-PT-100 execution

# this is for BenchKit: explicit launching of the test

cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-2270"
echo " Executing tool classicMC"
echo " Input is S_Dekker-PT-100, examination is ReachabilityBounds"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 4"
echo " Run identifier is r127st-blw3-143297563600060"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityBounds" = "ReachabilityComputeBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityBounds" != "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 "ReachabilityBounds.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityBounds.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityBounds.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 '' ReachabilityBounds.xml | cut -d '>' -f 2 | cut -d '<' -f 1 | sort -u) ; do
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 ;