About the Execution
Execution Summary | ||||
Max Memory Used (MB) |
CPU Usage (ms) | I/O Wait (ms) | Competition Result | Execution Status |
5468.64 | 488154 | 10.1 | MOVF | 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 tapaal
Input is SurpriseKanban-PT-0500, examination is ReachabilityDeadlock
Time confinement is 3600 seconds
Memory confinement is 6144 MBytes
Run identifier is r08ks-qhx2-140068996804684
=====================================================================
--------------------
content from stdout:
BK_START 1400755796998
**********************************************
* TAPAAL checking for ReachabilityDeadlock *
**********************************************
verifypn -n -r 1 -x 1 model.pnml ReachabilityDeadlock.xml
FORMULA Kanban-PT-0500-ReachabilityDeadlock-1
verifypn -n -r 1 -x 2 model.pnml ReachabilityDeadlock.xml
FORMULA Kanban-PT-0500-ReachabilityDeadlock-2
BK_STOP 1400756285073
--------------------
content from stderr:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
/home/mcc/BenchKit/BenchKit_head.sh: line 27: 1646 Aborted $VERIFYPN $1 "-x" $QUERY "model.pnml" $2
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
/home/mcc/BenchKit/BenchKit_head.sh: line 27: 1665 Aborted $VERIFYPN $1 "-x" $QUERY "model.pnml" $2
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="SurpriseKanban-PT-0500"
export BK_EXAMINATION="ReachabilityDeadlock"
export BK_TOOL="tapaal"
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/SurpriseKanban-PT-0500.tgz
mv SurpriseKanban-PT-0500 execution
# this is for BenchKit: explicit launching of the test
cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-1667"
echo " Executing tool tapaal"
echo " Input is SurpriseKanban-PT-0500, examination is ReachabilityDeadlock"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 6144 MBytes"
echo " Run identifier is r08ks-qhx2-140068996804684"
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 ;