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=Railroad-PT-050
export BK_EXAMINATION=ReachabilityDeadlock
export BK_TOOL=cunf
export BK_RESULT_DIR=/tmp
export BK_LOG_FILE=/tmp/BenchKit_head_log_file.1712
export BIN_DIR=/home/mcc/BenchKit/bin
cd /home/mcc/BenchKit/INPUTS/Railroad-PT-050
echo =====================================================================
echo ' Generated by BenchKit 1.0'
echo ' Executing tool cunf:'
echo ' Test is Railroad-PT-050, examination is ReachabilityDeadlock'
echo =====================================================================
echo
echo --------------------
echo 'content from stdout:'
echo
bash /home/mcc/BenchKit/BenchKit_head.sh

Execution Outputs of cunf for Railroad/050 (P/T)

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

execution on node 40: cluster1u42.lip6.fr (runId=136975220401133_n_40)
=====================================================================
runnning cunf on Railroad-PT-050 (ReachabilityDeadlock)
We got on stdout:
Probing ssh
Waiting ssh to respond
Ssh up and responding
=====================================================================
Generated by BenchKit 1.0
Executing tool cunf:
Test is Railroad-PT-050, examination is ReachabilityDeadlock
=====================================================================

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

START 1371574868