Difference: HAL (24 vs. 25)

Line: 1 to 1
	Short-term Target: CRC/initial release Frontend
Line: 107 to 107
	(JS) public static AlgorithmRun subclasses in most ExecutionManagers should probably be private (CF) Memory usage / CPU time monitoring in HAL of target algorithm runs, in order to report warnings on potential problems (like excessive swapping for example).
Changed:
< <	Bugs Reports
> >	Bug Reports
	(CN) JSC test reliability issue (compared to R) (CN) end-of-experiment hanging bug (GGA, multinode cluster runs) (JS) InnoDB SQL errors (CN): fixed 11/05/10
Line: 118 to 118
	(JS) HAL is not usable on WestGrid. We need a TorqueClusterExecutionManager. (JS) Algorithms with a requirement of a new directory for each run. (JS) one of the ExecutionManagers produces unstarted AlgorithmRuns
Changed:
< <	(CF) When HAL kills a target algorithm run, it does not also kill all child processes spawned by that run. This can leave zombies and all kinds of other very bad things after a period of time.
> >	(CF) When HAL kills a target algorithm run, it does not also kill all child processes spawned by that run. This can leave zombies and all kinds of other very bad things after a period of time. (CN): fixed 18/05/10

Short-term