This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 666

Summary: Erroneous time-lock
Product: UPPAAL Stratego Reporter: Danny Bøgsted Poulsen <dannybpoulsen>
Component: EngineAssignee: Marius Mikučionis <marius>
Status: RESOLVED FIXED    
Severity: normal CC: fshsho7
Priority: P5    
Version: 4.1.20-5   
Hardware: PC   
OS: Linux   
Architecture:
Attachments: Model

Description Danny Bøgsted Poulsen 2019-09-13 13:48:46 CEST
Created attachment 335 [details]
Model

Runnig the query
 strategy opt = minE (Process.timer) [<=50]: <> Process.STOP on the attached model results in the message 
"
State
( Process._id0 )
[ Process.timer=3.18742806482673 Process.c=3.18742806482673 ]
Process.loc=0 
is time-locked."


There shouldn't be a time-lock in the model in that particular state. There is no time-invariant on the location.
Comment 1 Marius Mikučionis 2019-09-30 12:17:34 CEST
This seems to be fixed on the working branch, so the fix is going to be released soon with stratego-6
Comment 2 Marius Mikučionis 2019-12-18 14:44:02 CET
The issue does not occur on this model using stratego-7, so I am closing.