fond
Model Checking Contest @ Petri Nets 2014
Tunis, Tunisia, June 24, 2014
Execution Report for Run r05kn-ovh1-140043891402228
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
1015.31 2999989 20.2 __________ 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 lola
Input is RwMutex-PT-r2000w0010, examination is ReachabilityCardinality
Time confinement is 3600 seconds
Memory confinement is 6144 MBytes
Run identifier is r05kn-ovh1-140043891402228
=====================================================================


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

BK_START 1401829355509
make: Nothing to be done for `prepare'.
ReachabilityCardinality @ execution
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-1 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-10 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-2 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-3 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-4 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-5 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-6 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-7 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-8 CANNOT_COMPUTE
FORMULA RwMutex-PT-r2000w0010-ReachabilityCardinality-9 CANNOT_COMPUTE

BK_STOP 1401832356204

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

make: [verify] Error 3 (ignored)

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-r2000w0010"
export BK_EXAMINATION="ReachabilityCardinality"
export BK_TOOL="lola"
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-r2000w0010.tgz
mv RwMutex-PT-r2000w0010 execution

# this is for BenchKit: explicit launching of the test

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