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 tapaalPAR
Input is LamportFastMutEx-PT-5, examination is CTLFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 4
Run identifier is r064kn-blw3-146358901400265
=====================================================================

--------------------
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 LamportFastMutEx-COL-5-CTLFireability-0
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-1
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-10
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-11
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-12
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-13
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-14
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-15
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-2
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-3
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-4
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-5
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-6
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-7
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-8
FORMULA_NAME LamportFastMutEx-COL-5-CTLFireability-9

=== Now, execution of the tool begins

BK_START 1463689091294


**********************************************
* TAPAAL Parallel verifying CTLFireability *
**********************************************
FORMULA LamportFastMutEx-COL-5-CTLFireability-0 TRUE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-1 FALSE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-2 TRUE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-3 FALSE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-4 TRUE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-5 TRUE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-6 FALSE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-7 TRUE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-8 FALSE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-9 FALSE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-11 FALSE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-13 TRUE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
FORMULA LamportFastMutEx-COL-5-CTLFireability-14 FALSE TECHNIQUES PARALLEL_PROCESSING EXPLICIT

BK_STOP 1463691480713

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

terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
/home/mcc/BenchKit/bin/ctl.sh: line 98: 412 Aborted timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLFireability.xml
/home/mcc/BenchKit/bin/ctl.sh: line 105: 428 Segmentation fault $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLFireability.xml
terminate called recursively
terminate called after throwing an instance of '/home/mcc/BenchKit/bin/ctl.sh: line 105: 435 Aborted $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLFireability.xml
/home/mcc/BenchKit/bin/ctl.sh: line 105: 440 Segmentation fault $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLFireability.xml

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="LamportFastMutEx-PT-5"
export BK_EXAMINATION="CTLFireability"
export BK_TOOL="tapaalPAR"
export BK_RESULT_DIR="/home/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/LamportFastMutEx-PT-5.tgz
mv LamportFastMutEx-PT-5 execution

# this is for BenchKit: explicit launching of the test

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