Details
-
Type:
Improvement
-
Status:
New
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: Current Version
-
Fix Version/s: None
-
Component/s: Evaluation Engine / Workers
-
Labels:
Description
In ACM-style contests, the user-visible result for a submit is "AC" when all tests pass, and some type of error status when one or more tests fail.
Currently, if multiple tests fail with different statuses, the "first" failure is shown.
Moreover, "first" is defined according to some internal order, different from the order visible in UI.
It'd be preferable if the status to display was chosen based on type of failure, and not order of tests.
For example, RE could take precedence over WA, then MLE, then TLE, etc.
Currently, if multiple tests fail with different statuses, the "first" failure is shown.
Moreover, "first" is defined according to some internal order, different from the order visible in UI.
It'd be preferable if the status to display was chosen based on type of failure, and not order of tests.
For example, RE could take precedence over WA, then MLE, then TLE, 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.
