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

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

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

execution on node 36: cluster1u38.lip6.fr (runId=136932120100715_n_36)
=====================================================================
runnning neco on Dekker-PT-010 (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-010, examination is StateSpace
=====================================================================

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

START 1369328863
======================================================
== Neco @ MCC'2013 ==
======================================================
Runing Dekker (PT), instance 010
STATE_SPACE 6144 TECHNIQUES EXPLICIT
STOP 1369328878

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


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