About the Execution of PeCan for CloudDeployment-PT-3a
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
314.690 | 4452.00 | 4793.00 | 29.70 | ???????????????? | normal |
Execution Chart
We display below the execution chart for this examination (boot time has been removed).
Trace from the execution
Waiting for the VM to be ready (probing ssh)
............
=====================================================================
Generated by BenchKit 2-2979
Executing tool pecan
Input is CloudDeployment-PT-3a, examination is ReachabilityCardinality
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r213su-blw3-146445843400367
=====================================================================
--------------------
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 CloudDeployment-PT-3a-ReachabilityCardinality-0
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-1
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-10
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-11
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-12
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-13
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-14
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-15
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-2
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-3
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-4
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-5
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-6
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-7
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-8
FORMULA_NAME CloudDeployment-PT-3a-ReachabilityCardinality-9
=== Now, execution of the tool begins
BK_START 1464771331640
=====================================================================
Generated by BenchKit MCC2016
Executing tool pecan:
Test is CloudDeployment-PT-3a, examination is ReachabilityCardinality
=====================================================================
--------------------
content from stdout:
START 1464771331
Xlib: extension "RANDR" missing on display ":99".
CloudDeploymentPT3aParsing Error: 'n12_p1' has been already defined as an LTL state condition at line 297 column 8. Please choose another name!
PAT finished successfully.
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-0
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-1
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-2
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-3
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-4
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-5
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-6
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-7
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-8
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-9
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-10
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-11
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-12
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-13
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-14
FORMULA CloudDeployment-PT-3a-ReachabilityCardinality-15
STOP 1464771336
--------------------
content from stderr:
--------------------
content from /home/hulinhub/BK_RESULTS/OUTPUTS/BenchKit_head_log_file.1831:
BK_STOP 1464771336092
--------------------
content from stderr:
cat: /home/hulinhub/BK_RESULTS/OUTPUTS/STDERR: No such file or directory
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="CloudDeployment-PT-3a"
export BK_EXAMINATION="ReachabilityCardinality"
export BK_TOOL="pecan"
export BK_RESULT_DIR="/home/hulinhub/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
tar xzf /home/mcc/BenchKit/INPUTS/CloudDeployment-PT-3a.tgz
mv CloudDeployment-PT-3a execution
# this is for BenchKit: explicit launching of the test
cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-2979"
echo " Executing tool pecan"
echo " Input is CloudDeployment-PT-3a, examination is ReachabilityCardinality"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r213su-blw3-146445843400367"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityCardinality" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityCardinality" != "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 "ReachabilityCardinality.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityCardinality.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityCardinality.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 ;