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=ReachabilityDeadlock
export BK_TOOL=lola_optimistic
export BK_RESULT_DIR=/tmp
export BK_LOG_FILE=/tmp/BenchKit_head_log_file.1657
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 lola_optimistic:'
echo ' Test is TokenRing-PT-020, examination is ReachabilityDeadlock'
echo =====================================================================
echo
echo --------------------
echo 'content from stdout:'
echo
bash /home/mcc/BenchKit/BenchKit_head.sh

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

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

START 1369907978
make: `model.pnml.lola' is up to date.
FORMULA p_1_deadlock FALSE TECHNIQUES EXPLICIT STATE_COMPRESSION STUBBORN_SETS