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

Execution Outputs of neco for TokenRing/020 (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=136989899501619_n_40)
=====================================================================
runnning neco on TokenRing-PT-020 (LTLMarkingComparison)
We got on stdout:
Probing ssh
Waiting ssh to respond
Ssh up and responding
=====================================================================
Generated by BenchKit 1.0
Executing tool neco:
Test is TokenRing-PT-020, examination is LTLMarkingComparison
=====================================================================

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

START 1369934793
======================================================
== Neco @ MCC'2013 ==
======================================================
Runing TokenRing (PT), instance 020
STOP 1369934793

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


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