fond
Model Checking Contest @ Petri Nets 2014
Tunis, Tunisia, June 24, 2014
Execution Report for Run r06ks-qhx2-140066506702497
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
165.72 1937 41.7 6144 -1 20 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-1667
Executing tool pnmc
Input is SurpriseDekker-PT-010, examination is StateSpace
Time confinement is 3600 seconds
Memory confinement is 6144 MBytes
Run identifier is r06ks-qhx2-140066506702497
=====================================================================


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

BK_START 1401830441649
STATE_SPACE 6144 -1 20 1 TECHNIQUES DECISION_DIAGRAMS

BK_STOP 1401830443412

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

6144 states
0.777469s
environ({'MAIL': '/var/mail/mcc', 'HOME': '/home/mcc', 'SSH_CLIENT': '10.0.2.2 46933 22', 'PATH': '/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games', '_': '/home/mcc/BenchKit/bin/pnmc.py', 'BK_INPUT': 'SurpriseDekker-PT-010', 'BK_RESULT_DIR': '/home/fko/BK_RESULTS/OUTPUTS', 'BIN_DIR': '/home/mcc/BenchKit/bin', 'BK_EXAMINATION': 'StateSpace', 'LOGNAME': 'mcc', 'BK_TIME_CONFINEMENT': '3600', 'SHELL': '/bin/bash', 'BK_TOOL': 'pnmc', 'SSH_CONNECTION': '10.0.2.2 46933 10.0.2.15 22', 'USER': 'mcc', 'SHLVL': '3', 'PWD': '/home/mcc/execution'})
Known False

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

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

# this is for BenchKit: explicit launching of the test

cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-1667"
echo " Executing tool pnmc"
echo " Input is SurpriseDekker-PT-010, examination is StateSpace"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 6144 MBytes"
echo " Run identifier is r06ks-qhx2-140066506702497"
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 ;