fond
Model Checking Contest 2024
14th edition, Geneva, Switzerland, June 25, 2024
Execution of r488-tall-171631133000591
Last Updated
July 7, 2024

About the Execution of LTSMin+red for DoubleLock-PT-p1s1

Execution Summary
Max Memory
Used (MB)
Time wait (ms) CPU Usage (ms) I/O Wait (ms) Computed Result Execution
Status
279.000 3022.00 8649.00 56.90 TFTFTTFTFTFFTTTT normal

Execution Chart

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

Trace from the execution

Formatting '/data/fkordon/mcc2024-input.r488-tall-171631133000591.qcow2', fmt=qcow2 size=4294967296 backing_file=/data/fkordon/mcc2024-input.qcow2 backing_fmt=qcow2 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Waiting for the VM to be ready (probing ssh)
.................
=====================================================================
Generated by BenchKit 2-5568
Executing tool ltsminxred
Input is DoubleLock-PT-p1s1, examination is ReachabilityFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 4
Run identifier is r488-tall-171631133000591
=====================================================================

--------------------
preparation of the directory to be used:
/home/mcc/execution
total 576K
-rw-r--r-- 1 mcc users 6.5K May 14 13:22 CTLCardinality.txt
-rw-r--r-- 1 mcc users 72K May 14 13:22 CTLCardinality.xml
-rw-r--r-- 1 mcc users 4.6K May 14 13:22 CTLFireability.txt
-rw-r--r-- 1 mcc users 39K May 14 13:22 CTLFireability.xml
-rw-r--r-- 1 mcc users 3.4K Apr 22 14:41 LTLCardinality.txt
-rw-r--r-- 1 mcc users 23K Apr 22 14:41 LTLCardinality.xml
-rw-r--r-- 1 mcc users 2.3K Apr 22 14:41 LTLFireability.txt
-rw-r--r-- 1 mcc users 19K Apr 22 14:41 LTLFireability.xml
-rw-r--r-- 1 mcc users 14K Apr 12 13:31 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users 153K Apr 12 13:31 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users 11K Apr 12 13:30 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users 93K Apr 12 13:30 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 1.5K May 19 07:11 UpperBounds.txt
-rw-r--r-- 1 mcc users 3.7K May 19 15:25 UpperBounds.xml
-rw-r--r-- 1 mcc users 6 May 18 16:42 equiv_col
-rw-r--r-- 1 mcc users 5 May 18 16:42 instance
-rw-r--r-- 1 mcc users 6 May 18 16:42 iscolored
-rw-r--r-- 1 mcc users 93K May 18 16:42 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 DoubleLock-PT-p1s1-ReachabilityFireability-2024-00
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-01
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-02
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-03
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-04
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-05
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-06
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-07
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-08
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-09
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-10
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-11
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-12
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-13
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-14
FORMULA_NAME DoubleLock-PT-p1s1-ReachabilityFireability-2024-15

=== Now, execution of the tool begins

BK_START 1717200867133

Invoking MCC driver with
BK_TOOL=ltsminxred
BK_EXAMINATION=ReachabilityFireability
BK_BIN_PATH=/home/mcc/BenchKit/bin/
BK_TIME_CONFINEMENT=3600
BK_INPUT=DoubleLock-PT-p1s1
BK_MEMORY_CONFINEMENT=16384
Applying reductions before tool ltsmin
Invoking reducer
Running Version 202405141337
[2024-06-01 00:14:28] [INFO ] Running its-tools with arguments : [-pnfolder, /home/mcc/execution, -examination, ReachabilityFireability, -timeout, 360, -rebuildPNML]
[2024-06-01 00:14:28] [INFO ] Parsing pnml file : /home/mcc/execution/model.pnml
[2024-06-01 00:14:28] [INFO ] Load time of PNML (sax parser for PT used): 71 ms
[2024-06-01 00:14:28] [INFO ] Transformed 64 places.
[2024-06-01 00:14:28] [INFO ] Transformed 204 transitions.
[2024-06-01 00:14:28] [INFO ] Parsed PT model containing 64 places and 204 transitions and 828 arcs in 159 ms.
Parsed 16 properties from file /home/mcc/execution/ReachabilityFireability.xml in 15 ms.
Working with output stream class java.io.PrintStream
Deduced a syphon composed of 8 places in 2 ms
Reduce places removed 8 places and 8 transitions.
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-05 TRUE TECHNIQUES TOPOLOGICAL INITIAL_STATE
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-15 TRUE TECHNIQUES TOPOLOGICAL INITIAL_STATE
RANDOM walk for 40000 steps (300 resets) in 1328 ms. (30 steps per ms) remains 8/14 properties
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-14 TRUE TECHNIQUES TOPOLOGICAL RANDOM_WALK
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-13 TRUE TECHNIQUES TOPOLOGICAL RANDOM_WALK
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-10 FALSE TECHNIQUES TOPOLOGICAL RANDOM_WALK
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-09 TRUE TECHNIQUES TOPOLOGICAL RANDOM_WALK
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-07 TRUE TECHNIQUES TOPOLOGICAL RANDOM_WALK
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-06 FALSE TECHNIQUES TOPOLOGICAL RANDOM_WALK
BEST_FIRST walk for 40004 steps (43 resets) in 554 ms. (72 steps per ms) remains 8/8 properties
BEST_FIRST walk for 40003 steps (25 resets) in 844 ms. (47 steps per ms) remains 8/8 properties
BEST_FIRST walk for 40003 steps (64 resets) in 115 ms. (344 steps per ms) remains 8/8 properties
BEST_FIRST walk for 40003 steps (8 resets) in 129 ms. (307 steps per ms) remains 8/8 properties
BEST_FIRST walk for 40004 steps (8 resets) in 163 ms. (243 steps per ms) remains 8/8 properties
BEST_FIRST walk for 40004 steps (62 resets) in 101 ms. (392 steps per ms) remains 8/8 properties
BEST_FIRST walk for 40004 steps (15 resets) in 106 ms. (373 steps per ms) remains 8/8 properties
BEST_FIRST walk for 40003 steps (10 resets) in 155 ms. (256 steps per ms) remains 8/8 properties
[2024-06-01 00:14:29] [INFO ] Flow matrix only has 148 transitions (discarded 48 similar events)
// Phase 1: matrix 148 rows 56 cols
[2024-06-01 00:14:29] [INFO ] Computed 4 invariants in 11 ms
[2024-06-01 00:14:29] [INFO ] State equation strengthened by 23 read => feed constraints.
All remaining problems are real, not stopping.
At refinement iteration 0 (INCLUDED_ONLY) 0/52 variables, 1/1 constraints. Problems are: Problem set: 0 solved, 8 unsolved
At refinement iteration 1 (INCLUDED_ONLY) 0/52 variables, 0/1 constraints. Problems are: Problem set: 0 solved, 8 unsolved
Problem DoubleLock-PT-p1s1-ReachabilityFireability-2024-00 is UNSAT
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-00 TRUE TECHNIQUES SMT_REFINEMENT
Problem DoubleLock-PT-p1s1-ReachabilityFireability-2024-01 is UNSAT
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-01 FALSE TECHNIQUES SMT_REFINEMENT
Problem DoubleLock-PT-p1s1-ReachabilityFireability-2024-02 is UNSAT
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-02 TRUE TECHNIQUES SMT_REFINEMENT
Problem DoubleLock-PT-p1s1-ReachabilityFireability-2024-03 is UNSAT
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-03 FALSE TECHNIQUES SMT_REFINEMENT
Problem DoubleLock-PT-p1s1-ReachabilityFireability-2024-04 is UNSAT
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-04 TRUE TECHNIQUES SMT_REFINEMENT
Problem DoubleLock-PT-p1s1-ReachabilityFireability-2024-08 is UNSAT
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-08 FALSE TECHNIQUES SMT_REFINEMENT
Problem DoubleLock-PT-p1s1-ReachabilityFireability-2024-11 is UNSAT
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-11 FALSE TECHNIQUES SMT_REFINEMENT
Problem DoubleLock-PT-p1s1-ReachabilityFireability-2024-12 is UNSAT
FORMULA DoubleLock-PT-p1s1-ReachabilityFireability-2024-12 TRUE TECHNIQUES SMT_REFINEMENT
After SMT solving in domain Real declared 53/204 variables, and 3 constraints, problems are : Problem set: 8 solved, 0 unsolved in 215 ms.
Refiners :[Positive P Invariants (semi-flows): 3/3 constraints, Generalized P Invariants (flows): 0/1 constraints, State Equation: 0/56 constraints, ReadFeed: 0/23 constraints, PredecessorRefiner: 8/8 constraints, Known Traps: 0/0 constraints]
After SMT, in 384ms problems are : Problem set: 8 solved, 0 unsolved
Skipping Parikh replay, no witness traces provided.
All properties solved without resorting to model-checking.
Total runtime 1708 ms.
ITS solved all properties within timeout

BK_STOP 1717200870155

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

+ ulimit -s 65536
+ [[ -z '' ]]
+ export LTSMIN_MEM_SIZE=8589934592
+ LTSMIN_MEM_SIZE=8589934592
+ export PYTHONPATH=/home/mcc/BenchKit/itstools/pylibs
+ PYTHONPATH=/home/mcc/BenchKit/itstools/pylibs
+ export LD_LIBRARY_PATH=/home/mcc/BenchKit/itstools/pylibs:
+ LD_LIBRARY_PATH=/home/mcc/BenchKit/itstools/pylibs:
++ sed s/.jar//
++ perl -pe 's/.*\.//g'
++ ls /home/mcc/BenchKit/bin//../reducer/bin//../../itstools//itstools/plugins/fr.lip6.move.gal.application.pnmcc_1.0.0.202405141337.jar
+ VERSION=202405141337
+ echo 'Running Version 202405141337'
+ /home/mcc/BenchKit/bin//../reducer/bin//../../itstools//itstools/its-tools -pnfolder /home/mcc/execution -examination ReachabilityFireability -timeout 360 -rebuildPNML

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="DoubleLock-PT-p1s1"
export BK_EXAMINATION="ReachabilityFireability"
export BK_TOOL="ltsminxred"
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-5568"
echo " Executing tool ltsminxred"
echo " Input is DoubleLock-PT-p1s1, examination is ReachabilityFireability"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 4"
echo " Run identifier is r488-tall-171631133000591"
echo "====================================================================="
echo
echo "--------------------"
echo "preparation of the directory to be used:"

tar xzf /home/mcc/BenchKit/INPUTS/DoubleLock-PT-p1s1.tgz
mv DoubleLock-PT-p1s1 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 ;