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

Execution Outputs of pnxdd for RessAllocation/R050C002 (P/T)

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

execution on node 22: quadhexa-2.u-paris10.fr (runId=136978036300014_n_22)
=====================================================================
runnning pnxdd on RessAllocation-PT-R050C002 (StateSpace)
We got on stdout:
Probing ssh
Waiting ssh to respond
Ssh up and responding
=====================================================================
Generated by BenchKit 1.0
Executing tool pnxdd:
Test is RessAllocation-PT-R050C002, examination is StateSpace
=====================================================================

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

START 1369781075
STATE_SPACE 2.92734e+16 TECHNIQUES DECISION_DIAGRAMS TOPOLOGICAL
STOP 1369781077

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


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