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
- All
- Comments
- History
- Activity
- Transitions
- Commits
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
