About the Execution of enPAC for PolyORBLF-PT-S06J04T04
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
141.050 | 14.00 | 89.00 | 0.00 | [undef] | Cannot compute |
Execution Chart
We display below the execution chart for this examination (boot time has been removed).
Trace from the execution
Formatting '/data/fkordon/mcc2019-input.r112-smll-155272312600356.qcow2', fmt=qcow2 size=4294967296 backing_file='/data/fkordon/mcc2019-input.qcow2' encryption=off cluster_size=65536 lazy_refcounts=off
Waiting for the VM to be ready (probing ssh)
...................
=====================================================================
Generated by BenchKit 2-3957
Executing tool enpac
Input is PolyORBLF-PT-S06J04T04, examination is CTLFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r112-smll-155272312600356
=====================================================================
--------------------
preparation of the directory to be used:
/home/mcc/execution
total 9.7M
-rw-r--r-- 1 mcc users 8.3K Feb 12 09:26 CTLCardinality.txt
-rw-r--r-- 1 mcc users 30K Feb 12 09:26 CTLCardinality.xml
-rw-r--r-- 1 mcc users 6.1K Feb 8 09:51 CTLFireability.txt
-rw-r--r-- 1 mcc users 28K Feb 8 09:51 CTLFireability.xml
-rw-r--r-- 1 mcc users 4.0K Mar 10 17:31 GenericPropertiesDefinition.xml
-rw-r--r-- 1 mcc users 5.9K Mar 10 17:31 GenericPropertiesVerdict.xml
-rw-r--r-- 1 mcc users 109 Feb 24 15:05 GlobalProperties.txt
-rw-r--r-- 1 mcc users 347 Feb 24 15:05 GlobalProperties.xml
-rw-r--r-- 1 mcc users 4.6K Feb 5 00:37 LTLCardinality.txt
-rw-r--r-- 1 mcc users 16K Feb 5 00:37 LTLCardinality.xml
-rw-r--r-- 1 mcc users 3.6K Feb 4 22:39 LTLFireability.txt
-rw-r--r-- 1 mcc users 15K Feb 4 22:39 LTLFireability.xml
-rw-r--r-- 1 mcc users 7.1K Feb 4 12:52 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users 25K Feb 4 12:52 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users 15K Feb 1 08:23 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users 56K Feb 1 08:23 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 2.9K Feb 4 22:23 UpperBounds.txt
-rw-r--r-- 1 mcc users 6.1K Feb 4 22:23 UpperBounds.xml
-rw-r--r-- 1 mcc users 5 Jan 29 09:34 equiv_col
-rw-r--r-- 1 mcc users 10 Jan 29 09:34 instance
-rw-r--r-- 1 mcc users 6 Jan 29 09:34 iscolored
-rw-r--r-- 1 mcc users 9.4M Mar 10 17:31 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-CTLFireability-00
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-01
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-02
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-03
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-04
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-05
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-06
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-07
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-08
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-09
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-10
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-11
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-12
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-13
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-14
FORMULA_NAME PolyORBLF-PT-S06J04T04-CTLFireability-15
=== Now, execution of the tool begins
BK_START 1552818332884
DO_NOT_COMPUTE
BK_STOP 1552818332898
--------------------
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="PolyORBLF-PT-S06J04T04"
export BK_EXAMINATION="CTLFireability"
export BK_TOOL="enpac"
export BK_RESULT_DIR="/tmp/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="3600"
export BK_MEMORY_CONFINEMENT="16384"
# 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-3957"
echo " Executing tool enpac"
echo " Input is PolyORBLF-PT-S06J04T04, examination is CTLFireability"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r112-smll-155272312600356"
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 [ "CTLFireability" = "GlobalProperties" ] ; then
rm -f GenericPropertiesVerdict.xml
fi
if [ "CTLFireability" = "UpperBounds" ] ; 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 [ "CTLFireability" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "CTLFireability" != "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 "CTLFireability.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property CTLFireability.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "CTLFireability.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
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 ;