Introduction

Execution Chart

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

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.

export BK_INPUT=TokenRing-PT-050
export BK_EXAMINATION=ReachabilityMarkingComparison
export BK_TOOL=greatSPN
export BK_RESULT_DIR=/tmp
export BK_LOG_FILE=/tmp/BenchKit_head_log_file.2015
export BIN_DIR=/home/mcc/BenchKit/bin
cd /home/mcc/BenchKit/INPUTS/TokenRing-PT-050
echo =====================================================================
echo ' Generated by BenchKit 1.0'
echo ' Executing tool greatSPN:'
echo ' Test is TokenRing-PT-050, examination is ReachabilityMarkingComparison'
echo =====================================================================
echo
echo --------------------
echo 'content from stdout:'
echo
bash /home/mcc/BenchKit/BenchKit_head.sh

Execution Outputs of greatSPN for TokenRing/050 (P/T)

This is useful if one wants to reexecute the tool in the VM from the submitted image disk.

execution on node 29: cluster1u31.lip6.fr (runId=136989901502112_n_29)
=====================================================================
runnning greatSPN on TokenRing-PT-050 (ReachabilityMarkingComparison)
We got on stdout:
Probing ssh
Waiting ssh to respond
Ssh up and responding
=====================================================================
Generated by BenchKit 1.0
Executing tool greatSPN:
Test is TokenRing-PT-050, examination is ReachabilityMarkingComparison
=====================================================================

--------------------
content from stdout:

START 1369929663
Runtime Error: fopen couldn't open model.def, in mode r
STOP 1369929663

--------------------
content from stderr:


--------------------
content from /tmp/BenchKit_head_log_file.2015: