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

Execution Outputs of neco for Dekker/050 (P/T)

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

execution on node 39: cluster1u41.lip6.fr (runId=136932120100718_n_39)
=====================================================================
runnning neco on Dekker-PT-050 (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 Dekker-PT-050, examination is StateSpace
=====================================================================

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

START 1369348855
======================================================
== Neco @ MCC'2013 ==
======================================================
Runing Dekker (PT), instance 050
CANNOT_COMPUTE
STOP 1369349172

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

Error: No net module in PYTHONPATH

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