Boundedness Checking Broken

Bug #809860 reported by Jiri Srba
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TAPAAL
Invalid
Critical
Unassigned
2.0
Fix Released
Critical
Unassigned
VerifyTAPN
Fix Released
Critical
Unassigned

Bug Description

Open that attached net, open the query and click on "Boundedness Check". It says it is bounded and the number
of tokens is optimized to -10 !

Related branches

Revision history for this message
Jiri Srba (srba) wrote :
Revision history for this message
Morten Jacobsen (mortenja) wrote :

I fixed the bug in the engine.

Changed in verifytapn:
importance: Undecided → Critical
milestone: none → 1.0.1
status: New → Fix Committed
Revision history for this message
Morten Jacobsen (mortenja) wrote :

Marking the bug as fixed in TAPAAL since this is really related to VerifyTAPN and not TAPAAL.

Changed in tapaal:
status: New → Fix Committed
status: Fix Committed → Invalid
Revision history for this message
Kenneth Yrke Jørgensen (yrke) wrote :

Changed the targing of the bug. As we release the engine together with the gui we still want to track the bug as affecting tapaal 2.0.

Jiri Srba (srba)
Changed in verifytapn:
status: Fix Committed → Fix Released
Changed in tapaal:
milestone: 2.1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.