Implement analyst evaluation mode #3025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kevinjil
force-pushed
the
analyst-eval
branch
2 times, most recently
from
299c4a2 to
60f966d
Compare
vmcj
reviewed
Jul 6, 2025
Kevinjil
force-pushed
the
analyst-eval
branch
from
60f966d to
2f6c3ec
Compare
tuupke
requested changes
Sep 3, 2025
Kevinjil
force-pushed
the
analyst-eval
branch
3 times, most recently
from
b1429a8 to
ca69da5
Compare
The idea behind this mode is that we are not really shadowing and trust the event feed results. However, we want to judge "interesting" runs locally to get useful information without the judging capacity to judge all testcases due to limited judgehost assignment. We do not consider 'TLE' or 'AC' interesting, as rerunning will not yield much more information. We consider 'WA' very interesting and prioritize the judging, but allow manual judging to overtake the priority. We consider 'CE' somewhat interesting, but downprioritize them a lot. For other verdicts, keep the normal priority.
Kevinjil
force-pushed
the
analyst-eval
branch
from
ca69da5 to
e609d99
Compare
When the QueueTask is already processed before the arrival of the upstream verdict, the udpated JudgeTask will never be picked up by a judge daemon. To ensure that the interesting run is actually picked up, create a new QueueTask. Note that, in case of an already existing unprocessed queue task, this should not break anything.
tuupke
reviewed
Sep 3, 2025
Otherwise there is a hidden dependency between the 'actual' constants, and these constants. So instead of `-9` use `JudgeTask::PRIORITY_HIGH + 1` and instead of `9` use `JudgeTask::PRIORITY_LOW - 1`. Suggested-by: Mart Pluijmaekers <[email protected]>
tuupke
approved these changes
Sep 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea behind this mode is that we are not really shadowing and trust the event feed results. However, we want to judge "interesting" runs locally to get useful information without the judging capacity to judge all testcases due to limited judgehost assignment.
We do not consider 'TLE' or 'AC' interesting, as rerunning will not yield much more information. We consider 'WA' very interesting and prioritize the judging, but allow manual judging to overtake the priority. We consider 'CE' somewhat interesting, but downprioritize them a lot. For other verdicts, keep the normal priority.