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

Execution Outputs of neco for SimpleLoadBal/02 (P/T)

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

execution on node 25: cluster1u27.lip6.fr (runId=136983930801316_n_25)
=====================================================================
runnning neco on SimpleLoadBal-PT-02 (StateSpace)
We got on stdout:
Probing ssh
Waiting ssh to respond
Ssh up and responding
=====================================================================
Generated by BenchKit 1.0
Executing tool neco:
Test is SimpleLoadBal-PT-02, examination is StateSpace
=====================================================================

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

START 1369867837
======================================================
== Neco @ MCC'2013 ==
======================================================
Runing SimpleLoadBal (PT), instance 02
STATE_SPACE 832 TECHNIQUES EXPLICIT
STOP 1369867844

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


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