fond
Model Checking Contest 2023
13th edition, Paris, France, April 26, 2023 (at TOOLympics II)
Execution of r483-tall-167912696100791
Last Updated
May 14, 2023

About the Execution of Smart for TwoPhaseLocking-PT-nC00010vD

Execution Summary
Max Memory
Used (MB)
Time wait (ms) CPU Usage (ms) I/O Wait (ms) Computed Result Execution
Status
157.424 1171.00 1030.00 20.00 TFTFTTTFFFFTFFTT normal

Execution Chart

We display below the execution chart for this examination (boot time has been removed).

Trace from the execution

Formatting '/data/fkordon/mcc2023-input.r483-tall-167912696100791.qcow2', fmt=qcow2 size=4294967296 backing_file=/data/fkordon/mcc2023-input.qcow2 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Waiting for the VM to be ready (probing ssh)
.....................................
=====================================================================
Generated by BenchKit 2-5348
Executing tool smart
Input is TwoPhaseLocking-PT-nC00010vD, examination is ReachabilityFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r483-tall-167912696100791
=====================================================================

--------------------
preparation of the directory to be used:
/home/mcc/execution
total 424K
-rw-r--r-- 1 mcc users 7.5K Feb 25 17:27 CTLCardinality.txt
-rw-r--r-- 1 mcc users 75K Feb 25 17:27 CTLCardinality.xml
-rw-r--r-- 1 mcc users 6.0K Feb 25 17:26 CTLFireability.txt
-rw-r--r-- 1 mcc users 55K Feb 25 17:26 CTLFireability.xml
-rw-r--r-- 1 mcc users 3.8K Feb 25 17:22 LTLCardinality.txt
-rw-r--r-- 1 mcc users 23K Feb 25 17:22 LTLCardinality.xml
-rw-r--r-- 1 mcc users 2.3K Feb 25 17:22 LTLFireability.txt
-rw-r--r-- 1 mcc users 15K Feb 25 17:22 LTLFireability.xml
-rw-r--r-- 1 mcc users 9.6K Feb 25 17:27 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users 91K Feb 25 17:27 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users 9.7K Feb 25 17:27 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users 82K Feb 25 17:27 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 1.8K Feb 25 17:22 UpperBounds.txt
-rw-r--r-- 1 mcc users 3.9K Feb 25 17:22 UpperBounds.xml
-rw-r--r-- 1 mcc users 6 Mar 5 18:23 equiv_col
-rw-r--r-- 1 mcc users 10 Mar 5 18:23 instance
-rw-r--r-- 1 mcc users 6 Mar 5 18:23 iscolored
-rw-r--r-- 1 mcc users 4.6K Mar 5 18:23 model.pnml

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

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

The expected result is a vector of booleans
BOOL_VECTOR

here is the order used to build the result vector(from text file)
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-00
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-01
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-02
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-03
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-04
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-05
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-06
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-07
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-08
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-09
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-10
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-11
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-12
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-13
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-14
FORMULA_NAME TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-15

=== Now, execution of the tool begins

BK_START 1679178912769

bash -c /home/mcc/BenchKit/BenchKit_head.sh 2> STDERR ; echo ; echo -n "BK_STOP " ; date -u +%s%3N
Invoking MCC driver with
BK_TOOL=smart
BK_EXAMINATION=ReachabilityFireability
BK_BIN_PATH=/home/mcc/BenchKit/bin/
BK_TIME_CONFINEMENT=3600
BK_INPUT=TwoPhaseLocking-PT-nC00010vD
Not applying reductions.
Model is PT
ReachabilityFireability PT
======================================================
========== this is Smart for the MCC'2018 ============
======================================================
Running TwoPhaseLocking (PT), instance nC00010vD
Examination ReachabilityFireability
Parser /home/mcc/BenchKit/bin//../smart/bin//parser/Fireability.jar
Model checker /home/mcc/BenchKit/bin//../smart/bin//rem_exec//smart

GOT IT HERE. BS
Petri model created: 8 places, 6 transitions, 18 arcs.
Final Score: 27.027
Took : 0 seconds
Reachability Fireability file is: ReachabilityFireability.xml
READY TO PARSE. BS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-00 TRUE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-01 FALSE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-02 TRUE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-03 FALSE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-04 TRUE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-05 TRUE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-06 TRUE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-07 FALSE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-08 FALSE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-09 FALSE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-10 FALSE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-11 TRUE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-12 FALSE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-13 FALSE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-14 TRUE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS
FORMULA TwoPhaseLocking-PT-nC00010vD-ReachabilityFireability-15 TRUE TECHNIQUES SEQUENTIAL_PROCESSING DECISION_DIAGRAMS

BK_STOP 1679178913940

--------------------
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="TwoPhaseLocking-PT-nC00010vD"
export BK_EXAMINATION="ReachabilityFireability"
export BK_TOOL="smart"
export BK_RESULT_DIR="/tmp/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="3600"
export BK_MEMORY_CONFINEMENT="16384"
export BK_BIN_PATH="/home/mcc/BenchKit/bin/"

# 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

# this is for BenchKit: explicit launching of the test
echo "====================================================================="
echo " Generated by BenchKit 2-5348"
echo " Executing tool smart"
echo " Input is TwoPhaseLocking-PT-nC00010vD, examination is ReachabilityFireability"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r483-tall-167912696100791"
echo "====================================================================="
echo
echo "--------------------"
echo "preparation of the directory to be used:"

tar xzf /home/mcc/BenchKit/INPUTS/TwoPhaseLocking-PT-nC00010vD.tgz
mv TwoPhaseLocking-PT-nC00010vD execution
cd execution
if [ "ReachabilityFireability" = "ReachabilityDeadlock" ] || [ "ReachabilityFireability" = "UpperBounds" ] || [ "ReachabilityFireability" = "QuasiLiveness" ] || [ "ReachabilityFireability" = "StableMarking" ] || [ "ReachabilityFireability" = "Liveness" ] || [ "ReachabilityFireability" = "OneSafe" ] || [ "ReachabilityFireability" = "StateSpace" ]; then
rm -f GenericPropertiesVerdict.xml
fi
pwd
ls -lh

echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityFireability" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityFireability" != "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 "ReachabilityFireability.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityFireability.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityFireability.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 '' ReachabilityFireability.xml | cut -d '>' -f 2 | cut -d '<' -f 1 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ "ReachabilityFireability" = "ReachabilityDeadlock" ] || [ "ReachabilityFireability" = "QuasiLiveness" ] || [ "ReachabilityFireability" = "StableMarking" ] || [ "ReachabilityFireability" = "Liveness" ] || [ "ReachabilityFireability" = "OneSafe" ] ; then
echo "FORMULA_NAME ReachabilityFireability"
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 ;