About the Execution of PeCan for Diffusion2D-PT-D05N150
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
1408.950 | 19303.00 | 19507.00 | 367.30 | TT??????TTT????? | 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 Diffusion2D-PT-D05N150, examination is ReachabilityCardinality
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r033kn-smll-146348021800088
=====================================================================
--------------------
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 Diffusion2D-PT-D05N150-ReachabilityCardinality-0
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-1
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-10
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-11
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-12
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-13
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-14
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-15
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-2
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-3
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-4
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-5
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-6
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-7
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-8
FORMULA_NAME Diffusion2D-PT-D05N150-ReachabilityCardinality-9
=== Now, execution of the tool begins
BK_START 1463847616332
=====================================================================
Generated by BenchKit MCC2016
Executing tool pecan:
Test is Diffusion2D-PT-D05N150, examination is ReachabilityCardinality
=====================================================================
--------------------
content from stdout:
START 1463847616
Xlib: extension "RANDR" missing on display ":99".
Diffusion2DPTD05N150mmap(...PROT_NONE...) failed
Stacktrace:
at (wrapper managed-to-native) System.GC.GetTotalMemory (bool) <0xffffffff>
at PAT.Common.Classes.ModuleInterface.VerificationOutput.StartVerification () <0x00033>
at PAT.Common.Classes.ModuleInterface.AssertionBase.InternalStart () <0x00057>
at PAT.Console.Program.RunOneSpec (string,string,System.IO.StreamWriter,System.Text.StringBuilder,bool,bool,int,int,string) <0x00187>
at PAT.Console.Program.Main (string[]) <0x0152f>
at (wrapper runtime-invoke)
Native stacktrace:
/usr/bin/mono() [0x80e16fc]
[0xb77d640c]
[0xb77d6424]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f) [0xb75f220f]
/lib/i386-linux-gnu/libc.so.6(abort+0x175) [0xb75f5855]
/usr/bin/mono() [0x8223e76]
/usr/bin/mono() [0x8225970]
/usr/bin/mono() [0x823785e]
/usr/bin/mono() [0x821c3bb]
/usr/bin/mono() [0x821c595]
/usr/bin/mono() [0x821c9dd]
/usr/bin/mono() [0x821ca5f]
/usr/bin/mono() [0x8150287]
[0xb3d0e7e8]
[0xb3d0dd54]
[0xb3d0d958]
[0xb5dcf100]
[0xb7093370]
[0xb709389f]
/usr/bin/mono() [0x8064c2c]
Debug info from gdb:
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
Aborted (core dumped)
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-0 TRUE TECHNIQUES EXPLICIT
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-1 TRUE TECHNIQUES EXPLICIT
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-2 TRUE TECHNIQUES EXPLICIT
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-3 TRUE TECHNIQUES EXPLICIT
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-4 TRUE TECHNIQUES EXPLICIT
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-5
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-6
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-7
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-8
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-9
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-10
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-11
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-12
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-13
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-14
FORMULA Diffusion2D-PT-D05N150-ReachabilityCardinality-15
STOP 1463847635
--------------------
content from stderr:
--------------------
content from /root/BK_RESULTS/OUTPUTS/BenchKit_head_log_file.1857:
BK_STOP 1463847635635
--------------------
content from stderr:
cat: /root/BK_RESULTS/OUTPUTS/STDERR: Permission denied
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="Diffusion2D-PT-D05N150"
export BK_EXAMINATION="ReachabilityCardinality"
export BK_TOOL="pecan"
export BK_RESULT_DIR="/root/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/Diffusion2D-PT-D05N150.tgz
mv Diffusion2D-PT-D05N150 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 Diffusion2D-PT-D05N150, 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 r033kn-smll-146348021800088"
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 ;