Project

General

Profile

Bug #4230

problem associating errors with particular execution

Added by Derik Barseghian over 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
provenance
Target version:
Start date:
07/08/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4230

Description

In SDF provenance records to the error table an exception thrown after the workflow stops. In PN, multiple exceptions may be thrown, and this happens during execution. Right now there's a problem with these errors getting recorded. Related/in addition: there's also difficulty knowing which execution errors are correlated with, since the same workflow may be executing and throwing errors in multiple windows. As Dan notes: Manager reports exceptions asynchronously; need a way to tie an exception to corresponding execution.


Related issues

Blocked by Kepler - Bug #4231: Workflow Run Manager - failed runs should be highlighted redResolved07/08/2009

Blocked by Kepler - Bug #4357: Workflow Run Manager does not mark last failed execution redResolved08/31/2009

History

#1 Updated by Derik Barseghian over 9 years ago

Dan, any updates for this bug?

#2 Updated by Daniel Crawl over 9 years ago

I have no updates for this bug.

It will take some effort since it requires changing Ptolemy's Manager and possibly the ExecutionListener interface. Currently ExecutionListeners receive error events asynchronously, but this makes it impossible to associate an error to a specific model execution.

Postpone this to a later release?

#3 Updated by Derik Barseghian over 9 years ago

changed title -- this isn't particular to the PN director, it can happen with other directors as well.

#4 Updated by Daniel Crawl over 9 years ago

Fixed.

#5 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4230

Also available in: Atom PDF