Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: Current Version
-
Fix Version/s: TAG 2013/14
-
Component/s: Evaluation Engine / Workers
-
Labels:None
Description
Rationale:
1. If the output checker crashes, we *really* want to be informed asap.
2. This would give a way of reporting errors like "the contestant's output is correct and better than model output".
Unfortunately, some checkers use exit code = 1 to report wrong answer. A possible workaround is to trigger System Error iff exit code >= 2.
1. If the output checker crashes, we *really* want to be informed asap.
2. This would give a way of reporting errors like "the contestant's output is correct and better than model output".
Unfortunately, some checkers use exit code = 1 to report wrong answer. A possible workaround is to trigger System Error iff exit code >= 2.
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.
