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-2265
Executing tool greatspn
Input is RwMutex-PT-r0010w0500, examination is ReachabilityComputeBounds
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r088kn-qhx2-143267642700075
=====================================================================

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

=== Data for post analysis generated by BenchKit (invocation template)

The expected result is a vector of positive values
NUM_VECTOR

here is the order used to build the result vector(from text file)
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-0
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-1
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-10
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-11
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-12
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-13
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-14
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-15
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-2
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-3
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-4
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-5
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-6
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-7
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-8
FORMULA_NAME RwMutex-PT-r0010w0500-ReachabilityComputeBounds-9

=== Now, execution of the tool begins

BK_START 1432833275295

=============================================================
== This is GreatSPN/Meddly, running for the MCC'2015 ==
=============================================================
Running execution (execution), instance execution
CONVERT PNML /home/mcc/execution/model.pnml
LOADING PETRI NET FILE /home/mcc/execution/model.pnml (PNML) ...
PNML VERSION 2009, P/T NET.
COLOR CLASSES: 0
CONSTANTS: 0
PLACES: 1030
TRANSITIONS: 1020
COLOR VARS: 0
MEASURES: 0
LOADING TIME: [User 0.124s, Sys 0.016s]


SAVING FILE /home/mcc/execution/model (.net / .def) ...
EXPORT TIME: [User 0.012s, Sys 0.004s]


COMPUTING STRUCTURAL BOUNDS.
CONVERT FORMULAE /home/mcc/execution/ReachabilityComputeBounds.xml INTO /home/mcc/execution/ReachabilityComputeBounds.rgmedd-ctl
/home/mcc/BenchKit/bin/GreatSPN/SOURCES/bin/RGMEDD model -h 200000000 -B 3 -FORCE-P -C -f /home/mcc/execution/ReachabilityComputeBounds.rgmedd-ctl
Using FORCE-PINV Heuristic for the variable ordering.
Setting MEDDLY cache to 200000000 bytes.
Opening file: model.bnd
----------------------------------------
Start firing rule encoding
----------------------------------------
----------------------------------------
End firing rule encoding

----------------------------------------
----------------------------------------
Start RS generation
----------------------------------------

Total Used Memory: 100804KB
RS size: 1524 (1524)
----------------------------------------
End RS generation
----------------------------------------

FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-0 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-1 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-2 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-3 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-4 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-5 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-6 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-7 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-8 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-9 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-10 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-11 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-12 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-13 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-14 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
FORMULA RwMutex-PT-r0010w0500-ReachabilityComputeBounds-15 1 TECHNIQUES DECISION_DIAGRAMS SEQUENTIAL_PROCESSING
Ok.

BK_STOP 1432833388225

--------------------
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-r0010w0500"
export BK_EXAMINATION="ReachabilityComputeBounds"
export BK_TOOL="greatspn"
export BK_RESULT_DIR="/home/fko/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="3600"
export BK_MEMORY_CONFINEMENT="16384"

# 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-r0010w0500.tgz
mv RwMutex-PT-r0010w0500 execution

# this is for BenchKit: explicit launching of the test

cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-2265"
echo " Executing tool greatspn"
echo " Input is RwMutex-PT-r0010w0500, examination is ReachabilityComputeBounds"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r088kn-qhx2-143267642700075"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityComputeBounds" = "ReachabilityComputeBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityComputeBounds" != "StateSpace" ] ; then
echo "The expected result is a vector of booleans"
echo BOOL_VECTOR
else
echo "no data necessary for post analysis"
fi
echo
if [ -f "ReachabilityComputeBounds.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityComputeBounds.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityComputeBounds.xml" ] ; then # for cunf (txt files deleted;-)
echo echo "here is the order used to build the result vector(from xml file)"
for x in $(grep '' ReachabilityComputeBounds.xml | cut -d '>' -f 2 | cut -d '<' -f 1 | sort -u) ; do
echo "FORMULA_NAME $x"
done
fi
echo
echo "=== Now, execution of the tool begins"
echo
echo -n "BK_START "
date -u +%s%3N
echo
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 ;