Add answers to questions from Luxor to manual/clars #2673
Closed
Conversation
This file contains 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
I would assume any system does this but it was a question last year.
Even when they are not, the jury should be aware and discuss it for other years.
eldering
reviewed
Sep 10, 2024
| DOMjudge will run your submissions on the test cases in a deterministic | ||
| order, i.e. if your program fails on the fourth case with wrong answer | ||
| and on the fifth case with run error, DOMjudge will report wrong | ||
| answer. It will not report the number of the test case that failed. |
There was a problem hiding this comment.
This is not always true and depends on the Results prio configuration setting. I don't think this should be included by default.
| The DOMjudge team would like your feedback. We do not | ||
| receive much feedback from participants. If you find | ||
| something lacking or have improvement ideas, please report | ||
| them. See https://www.domjudge.org/development. |
There was a problem hiding this comment.
What's the change here except reformatting?
| more consistent, for example we pin your submission to one core. | ||
| - DOMjudge does not define any special macros like ONLINE_JUDGE. | ||
| - For interactive problems, only your code runs inside of the sandbox and other processes | ||
| including the interactive problem interactor do not count towards memory or time limits for the submission. |
There was a problem hiding this comment.
I don't really understand what these do here in the default clarification answers (I think they should have been general clarifications sent out at the beginning of WFs), but they should not go into main.
| @@ -261,6 +261,8 @@ your program). | |||
| On the contest control system your program enters a queue, awaiting compilation, | |||
| execution and testing on one of the autojudges. | |||
|
|
|||
| Beware that if you submit multiple times in a short time interval the DOMjudge will determine which submission to judge based on both the submission time and how many other submission you have in queue to penalize spamming. | |||
There was a problem hiding this comment.
Suggested change
| Beware that if you submit multiple times in a short time interval the DOMjudge will determine which submission to judge based on both the submission time and how many other submission you have in queue to penalize spamming. | |
| Beware that if you submit multiple times in a short time interval, then DOMjudge will determine which submission to judge based on both the submission time and how many other submission you have in queue to penalize spamming. |
There was a problem hiding this comment.
Also, I'm not really sure this should go into the manual in main.
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.
I'll squash after approval.
No reason to merge it now, but I found it in the GDrive folder.