Wrong trace from workflow analysis
Bug #2035755 reported by
Jiri Srba
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| TAPAAL |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
Open the attached net and go to workflow dialog (under Tools/Workflow Analysis). Then add 15 extra tokens and run the analysis. The result is FALSE for soundness but the provided trace is wrong - when you open it in the simulator, the second occurence of T13 in the trace should consume two tokens but it consumes only one token - the trace is obviously wrong.
First of all the GUI should complain that the trace cannot be executed.
Second the engine should not return an invalid trace.
Revision history for this message
| Jiri Srba (srba) wrote | #1 |
Revision history for this message
| Jiri Srba (srba) wrote | #2 |
| Changed in tapaal: | |
| status: | New → Fix Committed |
To post a comment you must log in.
After the merge of the GUI check, it now reports errors on webserver TAPN, which is actually returning a good trace.