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-050
export BK_EXAMINATION=ReachabilityDeadlock
export BK_TOOL=lola
export BK_RESULT_DIR=/tmp
export BK_LOG_FILE=/tmp/BenchKit_head_log_file.1658
export BIN_DIR=/home/mcc/BenchKit/bin
BIN_DIR=/home/mcc/BenchKit/bin
cd /home/mcc/BenchKit/INPUTS/Dekker-PT-050
echo =====================================================================
echo ' Generated by BenchKit 1.0'
echo ' Executing tool lola:'
echo ' Test is Dekker-PT-050, examination is ReachabilityDeadlock'
echo =====================================================================
echo
echo --------------------
echo 'content from stdout:'
echo 'START 1369328123'

Execution Outputs of lola for Dekker/050 (P/T)

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

execution on node 27: cluster1u29.lip6.fr (runId=136932117000112_n_27)
=====================================================================
runnning lola on Dekker-PT-050 (ReachabilityDeadlock)
We got on stdout:
Probing ssh
Waiting ssh to respond
Ssh up and responding
=====================================================================
Generated by BenchKit 1.0
Executing tool lola:
Test is Dekker-PT-050, examination is ReachabilityDeadlock
=====================================================================

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

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