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

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

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

execution on node 24: cluster1u26.lip6.fr (runId=136980627001549_n_24)
=====================================================================
runnning neco on RwMutex-PT-r0010w0010 (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-r0010w0010, examination is StateSpace
=====================================================================

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

START 1369828632
======================================================
== Neco @ MCC'2013 ==
======================================================
Runing RwMutex (PT), instance r0010w0010
STATE_SPACE 1034 TECHNIQUES EXPLICIT
STOP 1369828641

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


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