About the Execution of Smart for CloudOpsManagement-PT-00002by00001
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
60.300 | 1310.00 | 1088.00 | 0.00 | T | 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.r081-smll-167814404900287.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 CloudOpsManagement-PT-00002by00001, examination is QuasiLiveness
Time confinement is 1800 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r081-smll-167814404900287
=====================================================================
--------------------
preparation of the directory to be used:
/home/mcc/execution
total 468K
-rw-r--r-- 1 mcc users 9.4K Feb 26 01:04 CTLCardinality.txt
-rw-r--r-- 1 mcc users 92K Feb 26 01:04 CTLCardinality.xml
-rw-r--r-- 1 mcc users 5.2K Feb 26 01:02 CTLFireability.txt
-rw-r--r-- 1 mcc users 40K Feb 26 01:02 CTLFireability.xml
-rw-r--r-- 1 mcc users 4.2K Jan 29 11:40 GenericPropertiesDefinition.xml
-rw-r--r-- 1 mcc users 4.5K Feb 25 15:45 LTLCardinality.txt
-rw-r--r-- 1 mcc users 26K Feb 25 15:45 LTLCardinality.xml
-rw-r--r-- 1 mcc users 2.7K Feb 25 15:45 LTLFireability.txt
-rw-r--r-- 1 mcc users 17K Feb 25 15:45 LTLFireability.xml
-rw-r--r-- 1 mcc users 14K Feb 26 01:05 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users 117K Feb 26 01:05 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users 8.4K Feb 26 01:04 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users 59K Feb 26 01:04 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 2.0K Feb 25 15:45 UpperBounds.txt
-rw-r--r-- 1 mcc users 4.0K Feb 25 15:45 UpperBounds.xml
-rw-r--r-- 1 mcc users 6 Mar 5 18:22 equiv_col
-rw-r--r-- 1 mcc users 13 Mar 5 18:22 instance
-rw-r--r-- 1 mcc users 6 Mar 5 18:22 iscolored
-rw-r--r-- 1 mcc users 17K Mar 5 18:22 model.pnml
--------------------
content from stdout:
=== Data for post analysis generated by BenchKit (invocation template)
The expected result is a vector of booleans
BOOL_VECTOR
FORMULA_NAME QuasiLiveness
=== Now, execution of the tool begins
BK_START 1678312773747
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=QuasiLiveness
BK_BIN_PATH=/home/mcc/BenchKit/bin/
BK_TIME_CONFINEMENT=1800
BK_INPUT=CloudOpsManagement-PT-00002by00001
Not applying reductions.
Model is PT
QuasiLiveness PT
======================================================
========== this is Smart for the MCC'2018 ============
======================================================
Running CloudOpsManagement (PT), instance 00002by00001
Examination QuasiLiveness
Parser /home/mcc/BenchKit/bin//../smart/bin//parser/QuasiLive.jar
Model checker /home/mcc/BenchKit/bin//../smart/bin//rem_exec//smart
PNML FILE: model.pnml
Petri model created: 27 places, 29 transitions, 94 arcs.
(potential((tk(P25)>=1)))
(potential((tk(P22)>=1) & (tk(P24)>=1)))
(potential((tk(P23)>=1)))
(potential((tk(P3)>=1) & (tk(P2)>=1)))
(potential((tk(P1)>=1) & (tk(P27)>=1)))
(potential((tk(P3)>=1)))
(potential((tk(P4)>=1)))
(potential((tk(P4)>=1) & (tk(P5)>=1)))
(potential((tk(P6)>=1) & (tk(P8)>=1) & (tk(P27)>=1)))
(potential((tk(P7)>=1) & (tk(P27)>=1)))
(potential((tk(P4)>=1) & (tk(P5)>=1)))
(potential((tk(P9)>=1) & (tk(P26)>=1)))
(potential((tk(P8)>=1)))
(potential((tk(P9)>=1) & (tk(P10)>=1)))
(potential((tk(P12)>=1) & (tk(P13)>=1) & (tk(P26)>=1)))
(potential((tk(P10)>=1) & (tk(P9)>=1)))
(potential((tk(P12)>=1)))
(potential((tk(P11)>=1) & (tk(P26)>=1)))
(potential((tk(P14)>=1) & (tk(P18)>=1) & (tk(P22)>=1)))
(potential((tk(P13)>=1)))
(potential((tk(P16)>=1)))
(potential((tk(P15)>=1)))
(potential((tk(P17)>=1) & (tk(P14)>=1)))
(potential((tk(P16)>=1)))
(potential((tk(P19)>=1)))
(potential((tk(P21)>=1)))
(potential((tk(P18)>=1) & (tk(P20)>=1)))
(potential((tk(P19)>=1)))
(potential((tk(P23)>=1)))
FORMULA QuasiLiveness TRUE TECHNIQUES IMPLICIT_RELATION DECISION_DIAGRAMS SATURATION
BK_STOP 1678312775057
--------------------
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="CloudOpsManagement-PT-00002by00001"
export BK_EXAMINATION="QuasiLiveness"
export BK_TOOL="smart"
export BK_RESULT_DIR="/tmp/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="1800"
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 CloudOpsManagement-PT-00002by00001, examination is QuasiLiveness"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r081-smll-167814404900287"
echo "====================================================================="
echo
echo "--------------------"
echo "preparation of the directory to be used:"
tar xzf /home/mcc/BenchKit/INPUTS/CloudOpsManagement-PT-00002by00001.tgz
mv CloudOpsManagement-PT-00002by00001 execution
cd execution
if [ "QuasiLiveness" = "ReachabilityDeadlock" ] || [ "QuasiLiveness" = "UpperBounds" ] || [ "QuasiLiveness" = "QuasiLiveness" ] || [ "QuasiLiveness" = "StableMarking" ] || [ "QuasiLiveness" = "Liveness" ] || [ "QuasiLiveness" = "OneSafe" ] || [ "QuasiLiveness" = "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 [ "QuasiLiveness" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "QuasiLiveness" != "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 "QuasiLiveness.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property QuasiLiveness.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "QuasiLiveness.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 '
echo "FORMULA_NAME $x"
done
elif [ "QuasiLiveness" = "ReachabilityDeadlock" ] || [ "QuasiLiveness" = "QuasiLiveness" ] || [ "QuasiLiveness" = "StableMarking" ] || [ "QuasiLiveness" = "Liveness" ] || [ "QuasiLiveness" = "OneSafe" ] ; then
echo "FORMULA_NAME QuasiLiveness"
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 ;