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=FMS-PT-010
export BK_EXAMINATION=ReachabilityDeadlock
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/FMS-PT-010
echo =====================================================================
echo ' Generated by BenchKit 1.0'
echo ' Executing tool greatSPN:'
echo ' Test is FMS-PT-010, examination is ReachabilityDeadlock'
echo =====================================================================
echo
echo --------------------
echo 'content from stdout:'
echo
bash /home/mcc/BenchKit/BenchKit_head.sh

Execution Outputs of greatSPN for FMS/010 (P/T)

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

execution on node 26: cluster1u28.lip6.fr (runId=136946435201371_n_26)
=====================================================================
runnning greatSPN on FMS-PT-010 (ReachabilityDeadlock)
We got on stdout:
Probing ssh
Waiting ssh to respond
Ssh up and responding
=====================================================================
Generated by BenchKit 1.0
Executing tool greatSPN:
Test is FMS-PT-010, examination is ReachabilityDeadlock
=====================================================================

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

START 1369478728
FORMULA p_1_deadlock FALSE TECHNIQUES DECISION_DIAGRAMS
FORMULA p_37_deadlock TRUE TECHNIQUES DECISION_DIAGRAMS
STOP 1369478729

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


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