Replies: 1 comment
-
|
For now, a simple test case is run in pub enum JudgeVerdict {
Accepted,
WrongAnswer,
TimeLimitExceeded,
IdlenessLimitExceeded,
RuntimeError,
PartialScore,
SystemError,
}And the function pub struct JudgeResultInfo {
pub verdict: JudgeVerdict,
pub time: i64,
pub memory: i64,
pub exit_status: i32,
pub checker_exit_status: i32,
}We simply use the exit status to decide the judging result. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Since we have completed the basic work flow of judger, we should define the judge verdict for further development and test.
There are two key tasks to do:
monitor.rs, therun_judgeandrun_interactfunction is expected to return the verdict directly, as well as some other status of the user program (or is there a better design?). A simplest way to implement it is to check the result fromsandbox.I want to discuss more details on it, like how to decide the verdict for TLE, and what kind of status should be returned.
Beta Was this translation helpful? Give feedback.
All reactions