Free cookie consent management tool by TermsFeed Policy Generator

Opened 16 years ago

Closed 16 years ago

Last modified 14 years ago

#633 closed defect (done)

Engines do not handle abortion of operators correctly

Reported by: gkronber Owned by: gkronber
Priority: medium Milestone: HeuristicLab 3.3.0
Component: Core Version: 3.2
Keywords: Cc:

Description

Aborted operators must reset the scope to a consistent state so that execution can be resumed with the same operator again. However, SequentialEngine resumes execution with the next operation on the stack. Instead the SequentialEngine should push the current operation back on the stack if an operator that supports abortion is aborted.

Change History (6)

comment:1 Changed 16 years ago by gkronber

  • Status changed from new to assigned

comment:2 Changed 16 years ago by gkronber

Fixed with r1847 for the SequentialEngine by:

  • introducing a Boolean property into IOperator that indicates if an operator supports abortion.
  • pushing the current operation back onto the execution stack of the SequentialEngine when the current operator can be aborted.

comment:3 Changed 16 years ago by gkronber

Reverted r1847 with r1851 after discussion with swagner. Instead each operator should decide independently what happens after abort and adapt the returned next operation accordingly.

comment:4 Changed 16 years ago by gkronber

  • Resolution set to fixed
  • Status changed from assigned to closed

Engines do not have to be adapted when each operator handles abort correctly.

comment:5 Changed 14 years ago by swagner

  • Milestone changed from Iteration 3 to Current

Milestone Iteration 3 deleted

comment:12 Changed 14 years ago by swagner

  • Milestone changed from Current to HeuristicLab 3.3.0

Milestone Current deleted

Note: See TracTickets for help on using tickets.