Execution Chart

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

Trace from the execution

Formatting '/data/fkordon/mcc2022-input.r295-smll-165463873200047.qcow2', fmt=qcow2 size=4294967296 backing_file=/data/fkordon/mcc2022-input.qcow2 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Waiting for the VM to be ready (probing ssh)
.............................................................................................................
=====================================================================
Generated by BenchKit 2-4028
Executing tool smpt
Input is CANInsertWithFailure-PT-050, examination is ReachabilityFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 4
Run identifier is r295-smll-165463873200047
=====================================================================

--------------------
preparation of the directory to be used:
/home/mcc/execution
total 16M
-rw-r--r-- 1 mcc users 8.4K May 30 15:24 CTLCardinality.txt
-rw-r--r-- 1 mcc users 67K May 30 15:24 CTLCardinality.xml
-rw-r--r-- 1 mcc users 5.3K May 30 15:13 CTLFireability.txt
-rw-r--r-- 1 mcc users 35K May 30 15:13 CTLFireability.xml
-rw-r--r-- 1 mcc users 4.7K May 25 12:58 LTLCardinality.txt
-rw-r--r-- 1 mcc users 25K May 25 12:58 LTLCardinality.xml
-rw-r--r-- 1 mcc users 3.3K May 25 12:58 LTLFireability.txt
-rw-r--r-- 1 mcc users 19K May 25 12:58 LTLFireability.xml
-rw-r--r-- 1 mcc users 1 May 29 12:20 NewModel
-rw-r--r-- 1 mcc users 16K May 30 15:34 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users 122K May 30 15:34 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users 16K May 30 15:29 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users 111K May 30 15:29 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 2.0K May 25 12:58 UpperBounds.txt
-rw-r--r-- 1 mcc users 4.0K May 25 12:58 UpperBounds.xml
-rw-r--r-- 1 mcc users 6 May 29 12:20 equiv_col
-rw-r--r-- 1 mcc users 4 May 29 12:20 instance
-rw-r--r-- 1 mcc users 6 May 29 12:20 iscolored
-rw-r--r-- 1 mcc users 16M May 29 12:20 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 CANInsertWithFailure-PT-050-ReachabilityFireability-00
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-01
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-02
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-03
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-04
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-05
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-06
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-07
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-08
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-09
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-10
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-11
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-12
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-13
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-14
FORMULA_NAME CANInsertWithFailure-PT-050-ReachabilityFireability-15

=== Now, execution of the tool begins

BK_START 1654657927087


FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-02 FALSE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-01 FALSE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-04 TRUE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-05 TRUE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-03 FALSE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-08 TRUE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-07 TRUE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-12 TRUE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-13 TRUE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-14 FALSE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-15 TRUE TECHNIQUES COLLATERAL_PROCESSING WALK

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-11 FALSE TECHNIQUES COLLATERAL_PROCESSING IMPLICIT SAT-SMT STATE_EQUATION

FORMULA CANInsertWithFailure-PT-050-ReachabilityFireability-06 FALSE TECHNIQUES COLLATERAL_PROCESSING WALK

BK_TIME_CONFINEMENT_REACHED

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

Reachability True
Host mcc2022
Colored False

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="CANInsertWithFailure-PT-050"
export BK_EXAMINATION="ReachabilityFireability"
export BK_TOOL="smpt"
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-4028"
echo " Executing tool smpt"
echo " Input is CANInsertWithFailure-PT-050, 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 r295-smll-165463873200047"
echo "====================================================================="
echo
echo "--------------------"
echo "preparation of the directory to be used:"

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