Skip to content
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.

Sign up for GitHub

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

Remove doc mention of judgehost restriction #2217

Merged
merged 1 commit into from
Nov 24, 2023
Merged

Remove doc mention of judgehost restriction #2217

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions doc/manual/judging.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,12 @@ The flow of an incoming submission is as follows.
checks, or accepted and stored as a *submission*.
#. The first available *judgehost* compiles, runs and checks
the submission. The outcome and outputs are stored as a
*judging* of this submission. Note that judgehosts may be
restricted to certain contests, languages and problems, so that it can be
the case that a judgehost is available, but not judging an available
submission.
*judging* of this submission. If parallel judging is enabled,
multiple judgehosts may pick up and work on the same submission
(if there is no queue of pending submissions).
#. To avoid starving other teams from judgehost resources,
submissions from teams that submit while they have other submissions
in the judge queue will get lower priority than a submission from a team that has no earlier submission being judged yet.
#. If verification is not required, the result is automatically
recorded and the team can view the result and the scoreboard is
updated (unless after the scoreboard freeze). A judge can
Expand Down
Loading