-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a working custom judge implementation #57
Conversation
# Conflicts: # jd4/case.py
The problem was _POSIX_C_SOURCE not defined in judge.c, causing fdopen() to be undefined, and for some reason the calling convention does not match... |
PROCESS_LIMIT), | ||
wait_cgroup(judge_cgroup_sock, | ||
judge_execute_task, | ||
DEFAULT_TIME_NS, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DEFAULT_TIME_NS is too short for some cases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, I think we need configurable time and memory limit for the custom judge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this configuration is global.
Remark: interactive cases are not supported. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder what's the data format for spj? |
No description provided.