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=GlobalRessAlloc-PT-05
export BK_EXAMINATION=ReachabilityDeadlock
export BK_TOOL=lola
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/GlobalRessAlloc-PT-05
echo =====================================================================
echo ' Generated by BenchKit 1.0'
echo ' Executing tool lola:'
echo ' Test is GlobalRessAlloc-PT-05, examination is ReachabilityDeadlock'
echo =====================================================================
echo
echo --------------------
echo 'content from stdout:'
echo
bash /home/mcc/BenchKit/BenchKit_head.sh

Execution Outputs of lola for GlobalRessAlloc/05 (P/T)

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

execution on node 12: quadhexa-2.u-paris10.fr (runId=136952152200018_n_12)
=====================================================================
runnning lola on GlobalRessAlloc-PT-05 (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 GlobalRessAlloc-PT-05, examination is ReachabilityDeadlock
=====================================================================

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

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