About the Execution of Marcie for PolyORBLF-PT-S06J04T04
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
7112.592 | 3600000.00 | 3600100.00 | 0.00 | [undef] | Time out reached |
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.r289-tall-167873940600591.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 marcie
Input is PolyORBLF-PT-S06J04T04, examination is ReachabilityFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r289-tall-167873940600591
=====================================================================
--------------------
preparation of the directory to be used:
/home/mcc/execution
total 8.2M
-rw-r--r-- 1 mcc users 13K Feb 26 13:55 CTLCardinality.txt
-rw-r--r-- 1 mcc users 88K Feb 26 13:55 CTLCardinality.xml
-rw-r--r-- 1 mcc users 115K Feb 26 13:52 CTLFireability.txt
-rw-r--r-- 1 mcc users 474K Feb 26 13:52 CTLFireability.xml
-rw-r--r-- 1 mcc users 4.2K Jan 29 11:40 GenericPropertiesDefinition.xml
-rw-r--r-- 1 mcc users 6.3K Jan 29 11:40 GenericPropertiesVerdict.xml
-rw-r--r-- 1 mcc users 7.8K Feb 25 16:35 LTLCardinality.txt
-rw-r--r-- 1 mcc users 36K Feb 25 16:35 LTLCardinality.xml
-rw-r--r-- 1 mcc users 39K Feb 25 16:35 LTLFireability.txt
-rw-r--r-- 1 mcc users 140K Feb 25 16:35 LTLFireability.xml
-rw-r--r-- 1 mcc users 19K Feb 26 14:07 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users 121K Feb 26 14:07 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users 39K Feb 26 14:05 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users 191K Feb 26 14:05 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 2.7K Feb 25 16:35 UpperBounds.txt
-rw-r--r-- 1 mcc users 5.4K Feb 25 16:35 UpperBounds.xml
-rw-r--r-- 1 mcc users 5 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 6.8M 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 PolyORBLF-PT-S06J04T04-ReachabilityFireability-00
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-01
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-02
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-03
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-04
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-05
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-06
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-07
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-08
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-09
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-10
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-11
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-12
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-13
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-14
FORMULA_NAME PolyORBLF-PT-S06J04T04-ReachabilityFireability-15
=== Now, execution of the tool begins
BK_START 1678798354122
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=marcie
BK_EXAMINATION=ReachabilityFireability
BK_BIN_PATH=/home/mcc/BenchKit/bin/
BK_TIME_CONFINEMENT=3600
BK_INPUT=PolyORBLF-PT-S06J04T04
Not applying reductions.
Model is PT
ReachabilityFireability PT
timeout --kill-after=10s --signal=SIGINT 1m for testing only
Marcie built on Linux at 2019-11-18.
A model checker for Generalized Stochastic Petri nets
authors: Alex Tovchigrechko (IDD package and CTL model checking)
Martin Schwarick (Symbolic numerical analysis and CSL model checking)
Christian Rohr (Simulative and approximative numerical model checking)
marcie@informatik.tu-cottbus.de
called as: /home/mcc/BenchKit/bin//../marcie/bin/marcie --net-file=model.pnml --mcc-file=ReachabilityFireability.xml --memory=6 --mcc-mode
parse successfull
net created successfully
Net: PolyORBLF_PT_S06J04T04
(NrP: 454 NrTr: 6994 NrArc: 59152)
parse formulas
formulas created successfully
place and transition orderings generation:0m 1.943sec
net check time: 0m 0.010sec
init dd package: 0m 2.771sec
TIME LIMIT: Killed by timeout after 3600 seconds
MemTotal: 16393932 kB
MemFree: 9106620 kB
After kill :
MemTotal: 16393932 kB
MemFree: 16172564 kB
BK_TIME_CONFINEMENT_REACHED
--------------------
content from stderr:
check for maximal unmarked siphon
ok
check for constant places
ok
check if there are places and transitions
ok
check if there are transitions without pre-places
ok
check if at least one transition is enabled in m0
ok
check if there are transitions that can never fire
ok
initing FirstDep: 0m 0.199sec
143012 212907 242767 184250 277756 381378 434414 551127 539945 550155 588664 546983 619757 554758 579683 775615 804940 825617 827266 841850 864265 915965 858569 867867 857541 882886 863766 832043 862943 869086 1275279
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="PolyORBLF-PT-S06J04T04"
export BK_EXAMINATION="ReachabilityFireability"
export BK_TOOL="marcie"
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 marcie"
echo " Input is PolyORBLF-PT-S06J04T04, 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 r289-tall-167873940600591"
echo "====================================================================="
echo
echo "--------------------"
echo "preparation of the directory to be used:"
tar xzf /home/mcc/BenchKit/INPUTS/PolyORBLF-PT-S06J04T04.tgz
mv PolyORBLF-PT-S06J04T04 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 '
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 ;