-
Notifications
You must be signed in to change notification settings - Fork 276
Interactive extra time #3053
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interactive extra time #3053
Conversation
6f91416 to
594135a
Compare
Currently interactive problems need more time due to the pipeline handling. Other problemtypes shouldn't have such requirements but if someone has a slower interactor or compare script for some types this can be helpful. So we both do this to not have `interactive` as special case and to provide people with the option due to unforseen setups.
594135a to
b668e96
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it best to first discuss how we best address this issue with the interactive validator sometimes requiring a lot of extra wallclock time. Ideally we solve that or just add wallclock extra overhead for interactive problems, not generic (also CPU time) overhead.
A side note: there are some problem color changes in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would keep this separate from timelimit_overshoot. Let's discuss in person?
Mostly as PoC,
I think this is helpful for the current state where interactive problems have overhead.
If we want to do this: