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-1668
Executing tool tapaal
Input is Diffusion2D-PT-D20N100, examination is ReachabilityComputeBounds
Time confinement is 3600 seconds
Memory confinement is 6144 MBytes
Run identifier is r28sr-ovh1-140203510400600
=====================================================================

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

BK_START 1402052159105

***********************************************
* TAPAAL verifying ReachabilityComputeBounds *
***********************************************

verifypn -n -r 1 -x 1 model.pnml ReachabilityComputeBounds.xml
FORMULA Diffusion2D-PT-D20N100-ReachabilityComputeBounds-1 CANNOT_COMPUTE

verifypn -n -r 1 -x 2 model.pnml ReachabilityComputeBounds.xml
FORMULA Diffusion2D-PT-D20N100-ReachabilityComputeBounds-2 CANNOT_COMPUTE

verifypn -n -r 1 -x 3 model.pnml ReachabilityComputeBounds.xml
FORMULA Diffusion2D-PT-D20N100-ReachabilityComputeBounds-3 CANNOT_COMPUTE

verifypn -n -r 1 -x 4 model.pnml ReachabilityComputeBounds.xml
FORMULA Diffusion2D-PT-D20N100-ReachabilityComputeBounds-4 CANNOT_COMPUTE

verifypn -n -r 1 -x 5 model.pnml ReachabilityComputeBounds.xml
FORMULA Diffusion2D-PT-D20N100-ReachabilityComputeBounds-5 CANNOT_COMPUTE

verifypn -n -r 1 -x 6 model.pnml ReachabilityComputeBounds.xml
FORMULA Diffusion2D-PT-D20N100-ReachabilityComputeBounds-6 CANNOT_COMPUTE

verifypn -n -r 1 -x 7 model.pnml ReachabilityComputeBounds.xml
FORMULA Diffusion2D-PT-D20N100-ReachabilityComputeBounds-7
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="Diffusion2D-PT-D20N100"
export BK_EXAMINATION="ReachabilityComputeBounds"
export BK_TOOL="tapaal"
export BK_RESULT_DIR="/srv/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/Diffusion2D-PT-D20N100.tgz
mv Diffusion2D-PT-D20N100 execution

# this is for BenchKit: explicit launching of the test

cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-1668"
echo " Executing tool tapaal"
echo " Input is Diffusion2D-PT-D20N100, examination is ReachabilityComputeBounds"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 6144 MBytes"
echo " Run identifier is r28sr-ovh1-140203510400600"
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 ;