Execution Chart

We display below the execution chart for this examination (boot time has been removed).

Trace from the execution

Waiting for the VM to be ready (probing ssh)
................
/home/mcc/execution
total 236K
-rw-r--r-- 1 mcc users 4.8K May 15 18:54 CTLCardinality.txt
-rw-r--r-- 1 mcc users 27K May 15 18:54 CTLCardinality.xml
-rw-r--r-- 1 mcc users 2.6K May 15 18:54 CTLFireability.txt
-rw-r--r-- 1 mcc users 15K May 15 18:54 CTLFireability.xml
-rw-r--r-- 1 mcc users 4.0K May 15 18:50 GenericPropertiesDefinition.xml
-rw-r--r-- 1 mcc users 6.3K May 15 18:50 GenericPropertiesVerdict.xml
-rw-r--r-- 1 mcc users 2.7K May 26 09:26 LTLCardinality.txt
-rw-r--r-- 1 mcc users 12K May 26 09:26 LTLCardinality.xml
-rw-r--r-- 1 mcc users 2.0K May 26 09:26 LTLFireability.txt
-rw-r--r-- 1 mcc users 8.4K May 26 09:26 LTLFireability.xml
-rw-r--r-- 1 mcc users 3.8K May 15 18:54 ReachabilityCardinality.txt
-rw-r--r-- 1 mcc users 18K May 15 18:54 ReachabilityCardinality.xml
-rw-r--r-- 1 mcc users 115 May 15 18:54 ReachabilityDeadlock.txt
-rw-r--r-- 1 mcc users 353 May 15 18:54 ReachabilityDeadlock.xml
-rw-r--r-- 1 mcc users 3.1K May 15 18:54 ReachabilityFireability.txt
-rw-r--r-- 1 mcc users 17K May 15 18:54 ReachabilityFireability.xml
-rw-r--r-- 1 mcc users 1.8K May 15 18:54 UpperBounds.txt
-rw-r--r-- 1 mcc users 3.8K May 15 18:54 UpperBounds.xml
-rw-r--r-- 1 mcc users 5 May 15 18:50 equiv_pt
-rw-r--r-- 1 mcc users 3 May 15 18:50 instance
-rw-r--r-- 1 mcc users 5 May 15 18:50 iscolored
-rw-r--r-- 1 mcc users 59K May 15 18:50 model.pnml
=====================================================================
Generated by BenchKit 2-3637
Executing tool tapaal
Input is DatabaseWithMutex-COL-40, examination is ReachabilityDeadlock
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 4
Run identifier is r084-blw3-152649951100034
=====================================================================

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

=== Data for post analysis generated by BenchKit (invocation template)

The expected result is a vector of booleans
BOOL_VECTOR

here is the order used to build the result vector(from text file)
FORMULA_NAME DatabaseWithMutex-COL-40-ReachabilityDeadlock-0

=== Now, execution of the tool begins

BK_START 1527680014769

tapaal
---> tapaal --- TAPAAL
Total timeout: 3590
Time left: 3590

**********************************************
* TAPAAL checking for ReachabilityDeadlock *
**********************************************
/home/mcc/tmp
/home/mcc/tmp/tmp.7bLHqIRPT9
/home/mcc/tmp/tmp.n45eVXDetG
Time left: 3590
---------------------------------------------------
Step -1: Stripping Colors
---------------------------------------------------
Verifying stripped models (1 in total)

Time left: 3590
---------------------------------------------------
Step 0: Parallel Simplification
---------------------------------------------------
Doing parallel simplification (1 in total)
Total simplification timout is 718 -- reduction timeout is 299
/home/mcc/BenchKit/bin/verifypn -n -q 718 -l 29 -d 299 -z 4 -s OverApprox --write-simplified /home/mcc/tmp/tmp.7bLHqIRPT9 --write-reduced /home/mcc/tmp/tmp.n45eVXDetG -x 1 ./model.pnml ./ReachabilityDeadlock.xml

Time left: 3588

---------------------------------------------------
Step 1: Parallel processing
---------------------------------------------------
Doing parallel verification of individual queries (1 in total)
Each query is verified by 4 parallel strategies for 598 seconds
------------------- QUERY 1 ----------------------
No solution found




Command terminated by signal 9
@@@513.87,12114464@@@


Time left: 2988
---------------------------------------------------
Step 2: Sequential processing
---------------------------------------------------
Remaining 1 queries are verified sequentially.
Each query is verified for a dynamic timeout (at least 0 seconds)
Time left: 2988
Time left: 2988
---------------------------------------------------
Step 4: Random Parallel processing
---------------------------------------------------
Doing random parallel verification of individual queries (1 in total)
Each query is verified by 4 parallel strategies for 2988 seconds
------------------- QUERY 1 ----------------------
No solution found




Command terminated by signal 9
@@@198.11,4145200@@@
Command terminated by signal 9
@@@273.23,5445332@@@
Command terminated by signal 9
@@@390.23,8172104@@@
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Command terminated by signal 6
@@@672.97,14962140@@@


Time left: 2315
Time left: 2315
---------------------------------------------------
Step 4: Random Parallel processing
---------------------------------------------------
Doing random parallel verification of individual queries (1 in total)
Each query is verified by 4 parallel strategies for 2315 seconds
------------------- QUERY 1 ----------------------
No solution found




Command terminated by signal 9
@@@227.52,5441376@@@
Command terminated by signal 9
@@@329.27,5457632@@@
Command terminated by signal 9
@@@441.49,8089672@@@
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Command terminated by signal 6
@@@715.37,14962368@@@


Time left: 1599
Time left: 1599
---------------------------------------------------
Step 4: Random Parallel processing
---------------------------------------------------
Doing random parallel verification of individual queries (1 in total)
Each query is verified by 4 parallel strategies for 1599 seconds
------------------- QUERY 1 ----------------------
No solution found




Command terminated by signal 9
@@@184.67,4135372@@@
Command terminated by signal 9
@@@251.41,5439888@@@
Command terminated by signal 9
@@@372.51,8142264@@@
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Command terminated by signal 6
@@@653.36,14960900@@@


Time left: 946
Time left: 946
---------------------------------------------------
Step 4: Random Parallel processing
---------------------------------------------------
Doing random parallel verification of individual queries (1 in total)
Each query is verified by 4 parallel strategies for 946 seconds
------------------- QUERY 1 ----------------------
No solution found




Command terminated by signal 9
@@@174.14,4080164@@@
Command terminated by signal 9
@@@236.86,5433768@@@
Command terminated by signal 9
@@@349.50,8090176@@@
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Command terminated by signal 6
@@@621.08,14961540@@@


Time left: 324
Time left: 324
---------------------------------------------------
Step 4: Random Parallel processing
---------------------------------------------------
Doing random parallel verification of individual queries (1 in total)
Each query is verified by 4 parallel strategies for 324 seconds
------------------- QUERY 1 ----------------------
No solution found




Command terminated by signal 9
@@@177.07,4210648@@@
Command terminated by signal 9
@@@228.68,5563492@@@


Time left: -2
Out of time, terminating!

BK_STOP 1527683606776

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

Warning: CPN OverApproximation is only available for Reachability queries without deadlock, negated fireability and UpperBounds, skipping DatabaseWithMutex-COL-40-ReachabilityDeadlock-0
Could not analyze the queries

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.

set -x
# this is for BenchKit: configuration of major elements for the test
export BK_INPUT="DatabaseWithMutex-COL-40"
export BK_EXAMINATION="ReachabilityDeadlock"
export BK_TOOL="tapaal"
export BK_RESULT_DIR="/tmp/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="3600"
export BK_MEMORY_CONFINEMENT="16384"

# this is specific to your benchmark or test

export BIN_DIR="$HOME/BenchKit/bin"

# remove the execution directoty if it exists (to avoid increse of .vmdk images)
if [ -d execution ] ; then
rm -rf execution
fi

tar xzf /home/mcc/BenchKit/INPUTS/DatabaseWithMutex-COL-40.tgz
mv DatabaseWithMutex-COL-40 execution
cd execution
pwd
ls -lh

# this is for BenchKit: explicit launching of the test
echo "====================================================================="
echo " Generated by BenchKit 2-3637"
echo " Executing tool tapaal"
echo " Input is DatabaseWithMutex-COL-40, examination is ReachabilityDeadlock"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 4"
echo " Run identifier is r084-blw3-152649951100034"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityDeadlock" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityDeadlock" != "StateSpace" ] ; then
echo "The expected result is a vector of booleans"
echo BOOL_VECTOR
else
echo "no data necessary for post analysis"
fi
echo
if [ -f "ReachabilityDeadlock.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityDeadlock.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityDeadlock.xml" ] ; then # for cunf (txt files deleted;-)
echo echo "here is the order used to build the result vector(from xml file)"
for x in $(grep '' ReachabilityDeadlock.xml | cut -d '>' -f 2 | cut -d '<' -f 1 | sort -u) ; do
echo "FORMULA_NAME $x"
done
fi
echo
echo "=== Now, execution of the tool begins"
echo
echo -n "BK_START "
date -u +%s%3N
echo
timeout -s 9 $BK_TIME_CONFINEMENT bash -c "/home/mcc/BenchKit/BenchKit_head.sh 2> STDERR ; echo ; echo -n \"BK_STOP \" ; date -u +%s%3N"
if [ $? -eq 137 ] ; then
echo
echo "BK_TIME_CONFINEMENT_REACHED"
fi
echo
echo "--------------------"
echo "content from stderr:"
echo
cat STDERR ;