Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Current Version
-
Fix Version/s: TAG 2016/17 Sprint 2
-
Component/s: Evaluation Engine / Workers
-
Labels:None
Description
When judging a task results in an exception in the worker, the stacktrace is sent back, and included in the sio2 system error details. However, it doesn't specify, from which worker the exception comes.
The worker (or the daemon to which it reports exceptions) should include the worker's name in the error message.
It would be really useful to know which worker generated the exception, especially in cases like MemoryError, NoSpaceOnDevice, etc.
The worker (or the daemon to which it reports exceptions) should include the worker's name in the error message.
It would be really useful to know which worker generated the exception, especially in cases like MemoryError, NoSpaceOnDevice, etc.
Activity
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
78d 22h 59m | 1 | Tadeusz Dudkiewicz | 2017-02-2 19:55 | |||||
|
781d 20h 42m | 1 | Szymon Acedański | 2019-03-26 16:37 |
