fond
Model Checking Contest @ Petri Nets 2014
Tunis, Tunisia, June 24, 2014
Execution Report for Run r05kn-ovh1-140043895206803
Last Updated
Sept. 1, 2014

About the Execution

Execution Summary
Max Memory
Used (MB)
CPU Usage (ms) I/O Wait (ms) Competition Result Execution
Status
64.51 68 9.8 TF________ 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-1668
Executing tool tapaal
Input is RwMutex-PT-r0010w0100, examination is ReachabilityDeadlock
Time confinement is 3600 seconds
Memory confinement is 6144 MBytes
Run identifier is r05kn-ovh1-140043895206803
=====================================================================


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

BK_START 1400473378517

**********************************************
* TAPAAL checking for ReachabilityDeadlock *
**********************************************

verifypn -n -r 1 -x 1 model.pnml ReachabilityDeadlock.xml
FORMULA RwMutex-PT-r0010w0100-ReachabilityDeadlock-1 TRUE TECHNIQUES EXPLICIT STRUCTURAL_REDUCTION
Query is satisfied.

verifypn -n -r 1 -x 2 model.pnml ReachabilityDeadlock.xml
FORMULA RwMutex-PT-r0010w0100-ReachabilityDeadlock-2 FALSE TECHNIQUES EXPLICIT STRUCTURAL_REDUCTION
Query is NOT satisfied.

BK_STOP 1400473378945

--------------------
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="RwMutex-PT-r0010w0100"
export BK_EXAMINATION="ReachabilityDeadlock"
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/RwMutex-PT-r0010w0100.tgz
mv RwMutex-PT-r0010w0100 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 RwMutex-PT-r0010w0100, examination is ReachabilityDeadlock"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 6144 MBytes"
echo " Run identifier is r05kn-ovh1-140043895206803"
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 ;