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=RwMutex-PT-r0010w0050
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/RwMutex-PT-r0010w0050
echo =====================================================================
echo ' Generated by BenchKit 1.0'
echo ' Executing tool neco:'
echo ' Test is RwMutex-PT-r0010w0050, examination is StateSpace'
echo =====================================================================
echo
echo --------------------
echo 'content from stdout:'
echo
bash /home/mcc/BenchKit/BenchKit_head.sh

Execution Outputs of neco for RwMutex/r0010w0050 (P/T)

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

execution on node 26: cluster1u28.lip6.fr (runId=136980627001551_n_26)
=====================================================================
runnning neco on RwMutex-PT-r0010w0050 (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 RwMutex-PT-r0010w0050, examination is StateSpace
=====================================================================

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

START 1369822972
======================================================
== Neco @ MCC'2013 ==
======================================================
Runing RwMutex (PT), instance r0010w0050
STATE_SPACE 1074 TECHNIQUES EXPLICIT
STOP 1369823002

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


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