Repository navigation
Add check for judge-specific limits - #514
Merged
Merged
Conversation
pehrsoderman
approved these changes
Nov 2, 2026
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
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.
We occasionally receive problem packages with outrageous limits. For example, someone may have (not unreasonably) assumed that the memory limit is in bytes, while the actual unit is MiB. The spec doesn't give hard bounds, for good reason.
This PR adds a new config file,
judge.yamlwhich allows a judge system to document what they want to support. Exceeding any of these limits will be a warning in problemtools. By default,judge.yamlis included with a conf suitable for Kattis. It is up to the judge system whether the limits documented this way are soft or hard. For Kattis, most of them are soft (so if you really need to go above a limit, discuss with us). I believe most of our limits are also roughly in line with other systems' preferences.Judge limits are implemented as a new "part" (so
-pcan select/deselect it). If you want different limits, simply drop ajudge.yamlin one of the usual directories. We also support it sitting above the problem directory (e.g., if you have a repo for problems you want to run on domjudge).Fixes #345