Only do multithread compilation of submissions actually used by -s #386
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
Matistjati
changed the title
gkreitz
reviewed
Jan 15, 2026
| def start_background_work(self, context: Context) -> None: | ||
| # Send off an early background compile job for each submission and | ||
| # validator, to avoid a bottleneck step at the start of each test run. | ||
| self.problem.output_validators.start_background_work(context) |
Contributor
There was a problem hiding this comment.
It can't have been intentional to remove this line (compiling the output validator), right?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently,
-jwill send off a precompile job for every submission, even if they arent matched by the-sflag passed. This is a real problem when you have ~100 C++ submissions, all with#include <bits/stdc++.h>. ....don't ask why 🙂 .