Execution Chart

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

Trace from the execution

Formatting '/data/fko/mcc2019-input.r170-oct2-155297750500293.qcow2', fmt=qcow2 size=4294967296 backing_file=/data/fko/mcc2019-input.qcow2 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Waiting for the VM to be ready (probing ssh)
....................
=====================================================================
Generated by BenchKit 2-3954
Executing tool lola
Input is TokenRing-COL-200, examination is CTLFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 4
Run identifier is r170-oct2-155297750500293
=====================================================================

--------------------
preparation of the directory to be used:
/home/mcc/execution
total 276K
-rw-r--r-- 1 mcc users 3.6K Feb 12 21:02 CTLCardinality.txt
-rw-r--r-- 1 mcc users 19K Feb 12 21:02 CTLCardinality.xml
-rw-r--r-- 1 mcc users 3.0K Feb 9 05:23 CTLFireability.txt
-rw-r--r-- 1 mcc users 17K Feb 9 05:23 CTLFireability.xml
-rw-r--r-- 1 mcc users 4.0K Mar 10 17:31 GenericPropertiesDefinition.xml
-rw-r--r-- 1 mcc users 6.2K Mar 10 17:31 GenericPropertiesVerdict.xml
-rw-r--r-- 1 mcc users 104 Feb 24 15:06 GlobalProperties.txt
-rw-r--r-- 1 mcc users 342 Feb 24 15:06 GlobalProperties.xml
-rw-r--r-- 1 mcc users 2.0K Feb 5 01:51 LTLCardinality.txt
-rw-r--r-- 1 mcc users 8.0K Feb 5 01:51 LTLCardinality.xml
-rw-r--r-- 1 mcc users 2.0K Feb 4 22:50 LTLFireability.txt
-rw-r--r-- 1 mcc users 8.6K Feb 4 22:50 LTLFireability.xml
-rw-r--r-- 1 mcc users 3.6K Feb 4 22:10 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users 18K Feb 4 22:10 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users 3.1K Feb 1 23:14 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users 17K Feb 1 23:14 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 1.6K Feb 4 22:31 UpperBounds.txt
-rw-r--r-- 1 mcc users 3.7K Feb 4 22:31 UpperBounds.xml
-rw-r--r-- 1 mcc users 5 Jan 29 09:35 equiv_pt
-rw-r--r-- 1 mcc users 4 Jan 29 09:35 instance
-rw-r--r-- 1 mcc users 5 Jan 29 09:35 iscolored
-rw-r--r-- 1 mcc users 109K 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 TokenRing-COL-200-CTLFireability-00
FORMULA_NAME TokenRing-COL-200-CTLFireability-01
FORMULA_NAME TokenRing-COL-200-CTLFireability-02
FORMULA_NAME TokenRing-COL-200-CTLFireability-03
FORMULA_NAME TokenRing-COL-200-CTLFireability-04
FORMULA_NAME TokenRing-COL-200-CTLFireability-05
FORMULA_NAME TokenRing-COL-200-CTLFireability-06
FORMULA_NAME TokenRing-COL-200-CTLFireability-07
FORMULA_NAME TokenRing-COL-200-CTLFireability-08
FORMULA_NAME TokenRing-COL-200-CTLFireability-09
FORMULA_NAME TokenRing-COL-200-CTLFireability-10
FORMULA_NAME TokenRing-COL-200-CTLFireability-11
FORMULA_NAME TokenRing-COL-200-CTLFireability-12
FORMULA_NAME TokenRing-COL-200-CTLFireability-13
FORMULA_NAME TokenRing-COL-200-CTLFireability-14
FORMULA_NAME TokenRing-COL-200-CTLFireability-15

=== Now, execution of the tool begins

BK_START 1553116814284

info: Time: 3600 - MCC
vrfy: Checking CTLFireability @ TokenRing-COL-200 @ 3570 seconds
vrfy: finished
info: timeLeft: -24
rslt: Output for CTLFireability @ TokenRing-COL-200

{
"build":
{
"architecture": 64,
"assertions": false,
"build_hostname": "mcc2019",
"build_system": "x86_64-unknown-linux-gnu",
"optimizations": true,
"package_version": "2.0",
"svn_version": "3189M"
},
"call":
{
"exec_host": "mcc2019",
"parameters":
[
"--pnmlnet",
"model.pnml",
"--xmlformula",
"--formula=CTLFireability.xml",
"--mcc",
"--donotcomputecapacities",
"--encoder=simplecompressed",
"--check=modelchecking",
"--stubborn=tarjan",
"--stateequation=par",
"--quickchecks",
"--timelimit=3570",
"--localtimelimit=0",
"--preference=force_ctl",
"--json=CTLFireability.json",
"--jsoninclude=formula,formulastat,net"
],
"starttime": "Wed Mar 20 21:20:14 2019
",
"timelimit": 3570
},
"child": null,
"exit":
{
"error": null,
"memory": 5866484,
"runtime": 3570.000000,
"signal": null,
"timelimitreached": true
},
"files":
{
"net": "model.pnml"
}
}
lola: LoLA will run for 3570 seconds at most (--timelimit)
lola: NET
lola: input: PNML file (--pnml)
lola: reading net from model.pnml
lola: reading pnml
lola: PNML file contains High-Level net
lola: Places: 40401, Transitions: 8040201
lola: @ trans mainprocess
lola: @ trans otherprocess
lola: time limit reached - aborting
lola: memory consumption: 5866484 KB
lola: time consumption: 3570 seconds
lola: print data as JSON (--json)
lola: writing JSON to CTLFireability.json
lola: closed JSON file CTLFireability.json
rslt: finished

BK_STOP 1553120408892

--------------------
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="TokenRing-COL-200"
export BK_EXAMINATION="CTLFireability"
export BK_TOOL="lola"
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-3954"
echo " Executing tool lola"
echo " Input is TokenRing-COL-200, examination is CTLFireability"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 4"
echo " Run identifier is r170-oct2-155297750500293"
echo "====================================================================="
echo
echo "--------------------"
echo "preparation of the directory to be used:"

tar xzf /home/mcc/BenchKit/INPUTS/TokenRing-COL-200.tgz
mv TokenRing-COL-200 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 '' CTLFireability.xml | cut -d '>' -f 2 | cut -d '<' -f 1 | sort -u) ; do
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 ;