About the Execution of Tapaal(PAR) for AutoFlight-PT-96b
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
14294.950 | 3600000.00 | 7605944.00 | 957.90 | ??????F????????? | 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-2979
Executing tool tapaalPAR
Input is AutoFlight-PT-96b, examination is CTLCardinality
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 4
Run identifier is r208su-blw3-146445823500336
=====================================================================
--------------------
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 AutoFlight-PT-96b-CTLCardinality-0
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-1
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-10
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-11
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-12
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-13
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-14
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-15
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-2
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-3
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-4
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-5
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-6
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-7
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-8
FORMULA_NAME AutoFlight-PT-96b-CTLCardinality-9
=== Now, execution of the tool begins
BK_START 1464634530231
**********************************************
* TAPAAL Parallel verifying CTLCardinality *
**********************************************
FORMULA AutoFlight-PT-96b-CTLCardinality-14 FALSE TECHNIQUES PARALLEL_PROCESSING EXPLICIT
BK_TIME_CONFINEMENT_REACHED
--------------------
content from stderr:
/home/mcc/BenchKit/bin/ctl.sh: line 47: 358 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 370 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 372 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 374 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 376 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 379 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 381 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 383 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 385 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 388 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 390 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 392 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 394 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 396 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 47: 405 Segmentation fault timeout $TIMEOUT_SEQ $VERIFYPN_SEQ -ctl czero -s DFS -n -x $i model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 440 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 453 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 459 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 473 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 479 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 492 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 498 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 505 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 511 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.xml
/home/mcc/BenchKit/bin/ctl.sh: line 63: 517 Segmentation fault timeout $TIMEOUT_PAR $VERIFYPN_PAR -ctl par -s DFS -n -x $k model.pnml CTLCardinality.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="AutoFlight-PT-96b"
export BK_EXAMINATION="CTLCardinality"
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/AutoFlight-PT-96b.tgz
mv AutoFlight-PT-96b 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 AutoFlight-PT-96b, examination is CTLCardinality"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 4"
echo " Run identifier is r208su-blw3-146445823500336"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "CTLCardinality" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "CTLCardinality" != "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 "CTLCardinality.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property CTLCardinality.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "CTLCardinality.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 ;