About the Execution of 2021-gold for CANInsertWithFailure-PT-070
| Execution Summary | |||||
| Max Memory Used (MB)  | 
      Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status  | 
   
| 0.000 | 3600000.00 | 0.00 | 0.00 | [undef] | Time out reached | 
Execution Chart
Sorry, for this execution, no execution chart could be reported.
Trace from the execution
Formatting '/data/fkordon/mcc2022-input.r303-smll-165463877700008.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 gold2021
    Input is CANInsertWithFailure-PT-070, examination is StateSpace
    Time confinement is 3600 seconds
    Memory confinement is 16384 MBytes
    Number of cores is 1
    Run identifier is r303-smll-165463877700008
=====================================================================
--------------------
preparation of the directory to be used:
/home/mcc/execution
total 30M
-rw-r--r-- 1 mcc users 9.0K May 30 15:37 CTLCardinality.txt
-rw-r--r-- 1 mcc users  79K May 30 15:37 CTLCardinality.xml
-rw-r--r-- 1 mcc users 6.4K May 30 15:27 CTLFireability.txt
-rw-r--r-- 1 mcc users  43K May 30 15:27 CTLFireability.xml
-rw-r--r-- 1 mcc users 4.4K May 25 12:59 LTLCardinality.txt
-rw-r--r-- 1 mcc users  25K May 25 12:59 LTLCardinality.xml
-rw-r--r-- 1 mcc users 3.2K May 25 12:59 LTLFireability.txt
-rw-r--r-- 1 mcc users  18K May 25 12:59 LTLFireability.xml
-rw-r--r-- 1 mcc users    1 May 29 12:20 NewModel
-rw-r--r-- 1 mcc users  13K May 30 15:45 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users  97K May 30 15:45 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users  15K May 30 15:40 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users  98K May 30 15:40 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 2.0K May 25 12:59 UpperBounds.txt
-rw-r--r-- 1 mcc users 4.0K May 25 12:59 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  30M May 29 12:20 model.pnml
--------------------
content from stdout:
=== Data for post analysis generated by BenchKit (invocation template)
no data necessary for post analysis
=== Now, execution of the tool begins
BK_START 1654673193810
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-070"
export BK_EXAMINATION="StateSpace"
export BK_TOOL="gold2021"
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 gold2021"
echo "    Input is CANInsertWithFailure-PT-070, examination is StateSpace"
echo "    Time confinement is $BK_TIME_CONFINEMENT seconds"
echo "    Memory confinement is 16384 MBytes"
echo "    Number of cores is 1"
echo "    Run identifier is r303-smll-165463877700008"
echo "====================================================================="
echo
echo "--------------------"
echo "preparation of the directory to be used:"
tar xzf /home/mcc/BenchKit/INPUTS/CANInsertWithFailure-PT-070.tgz
mv CANInsertWithFailure-PT-070 execution
cd execution
if [ "StateSpace" = "ReachabilityDeadlock" ] || [ "StateSpace" = "UpperBounds" ] || [ "StateSpace" = "QuasiLiveness" ] || [ "StateSpace" = "StableMarking" ] || [ "StateSpace" = "Liveness" ] || [ "StateSpace" = "OneSafe" ] || [ "StateSpace" = "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 [ "StateSpace" = "UpperBounds" ] ; then
	echo "The expected result is a vector of positive values"
	echo NUM_VECTOR
elif [ "StateSpace" != "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 "StateSpace.txt" ] ; then
	echo "here is the order used to build the result vector(from text file)"
	for x in $(grep Property StateSpace.txt | cut -d ' ' -f 2 | sort -u) ; do
		echo "FORMULA_NAME $x"
	done
elif [ -f "StateSpace.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 [ "StateSpace" = "ReachabilityDeadlock" ] || [ "StateSpace" = "QuasiLiveness" ] || [ "StateSpace" = "StableMarking" ] || [ "StateSpace" = "Liveness" ] || [ "StateSpace" = "OneSafe" ] ; then
	echo "FORMULA_NAME StateSpace"
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 ;
