#155 closed defect (done)
Exceptions in engines are not handled correctly
| Reported by: | gkronber | Owned by: | gkronber |
|---|---|---|---|
| Priority: | medium | Milestone: | HeuristicLab 3.3.0 |
| Component: | ZZZ OBSOLETE: DistributedEngine | Version: | 3.1 |
| Keywords: | Cc: |
Description
The distributed-engine doesn't handle results from aborted engines correctly. This is a problem when an engine running on a grid-client is aborted because of an exception. When the result is merged at the distributed-engine the scope-tree is in an inconsistent state and the distributed-engine can't resume execution.
Change History (6)
comment:1 Changed 17 years ago by gkronber
- Status changed from new to assigned
comment:2 Changed 17 years ago by gkronber
comment:3 Changed 17 years ago by gkronber
- Resolution set to fixed
- Status changed from assigned to closed
test runs were successful
comment:4 Changed 16 years ago by swagner
- Milestone changed from 3.1 to Iteration 0
Milestone 3.1 deleted
comment:5 Changed 14 years ago by swagner
- Milestone changed from Iteration 0 to Current
Milestone Iteration 0 deleted
comment:11 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.
addressed the problem with r281
"operations that failed at a grid-client are pushed back onto the stack again to force local execution. If they fail locally as well the user will get the usual error dialog and can fix the bug (and save/load the engine as usual)."
Waiting for the result of a test with !MetaGP engine of pspitzli ...