fond
Model Checking Contest @ Petri Nets 2014
Tunis, Tunisia, June 24, 2014
Execution Report for Run r05kn-ovh1-140043892904018
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
821.79 33999 30.3 2024 -1 1020 1 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 pnmc
Input is RwMutex-PT-r0010w1000, examination is StateSpace
Time confinement is 3600 seconds
Memory confinement is 6144 MBytes
Run identifier is r05kn-ovh1-140043892904018
=====================================================================


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

BK_START 1401824829429
STATE_SPACE 2024 -1 1020 1 TECHNIQUES DECISION_DIAGRAMS

BK_STOP 1401824864329

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

2024 states
34.0498s
environ({'BIN_DIR': '/home/mcc/BenchKit/bin', 'SHLVL': '3', 'USER': 'mcc', 'PWD': '/home/mcc/execution', 'LANG': 'en_US.UTF-8', 'LOGNAME': 'mcc', 'BK_INPUT': 'RwMutex-PT-r0010w1000', 'SSH_CONNECTION': '10.0.2.2 49267 10.0.2.15 22', 'BK_RESULT_DIR': '/srv/fko/BK_RESULTS/OUTPUTS', 'PATH': '/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games', 'SHELL': '/bin/bash', 'BK_TIME_CONFINEMENT': '3600', 'HOME': '/home/mcc', 'SSH_CLIENT': '10.0.2.2 49267 22', 'MAIL': '/var/mail/mcc', 'BK_EXAMINATION': 'StateSpace', 'BK_TOOL': 'pnmc', '_': '/home/mcc/BenchKit/bin/pnmc.py'})
Known True

['/usr/local/bin/pnmc', '--fast-exit', '--hom-cache-size=4000000', '--results-json=results.json', '--pnml', '/home/mcc/execution/model.pnml', '--order-force']

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-r0010w1000"
export BK_EXAMINATION="StateSpace"
export BK_TOOL="pnmc"
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-r0010w1000.tgz
mv RwMutex-PT-r0010w1000 execution

# this is for BenchKit: explicit launching of the test

cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-1668"
echo " Executing tool pnmc"
echo " Input is RwMutex-PT-r0010w1000, examination is StateSpace"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 6144 MBytes"
echo " Run identifier is r05kn-ovh1-140043892904018"
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 ;