You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Copy file name to clipboardExpand all lines: etc/db-config.yaml
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -118,12 +118,13 @@
118
118
type: int
119
119
default_value: 1
120
120
public: false
121
-
description: Lazy evaluation of results? If enabled, stops judging as soon as a highest priority result is found, otherwise always all testcases will be judged. On request will not auto-start judging and is typically used when running as analyst system.
121
+
description: Lazy evaluation of results? If enabled, stops judging as soon as a highest priority result is found, otherwise always all testcases will be judged. On request will not auto-start judging. Analyst mode tries to judge only interesting testcases.
122
122
options:
123
123
1: Lazy
124
124
2: Full judging
125
125
3: Only on request
126
-
regex: /^[123]$/
126
+
4: Analyst mode
127
+
regex: /^[1234]$/
127
128
error_message: A value between 1 and 3 is required.
0 commit comments