judge solutions for longer than timelimit

[eldering]

Judge requests for longer than the timelimit. Can show judges if it would finish just a bit over it or if it's a real overshoot.

[eldering]

Imported from trac issue 100. Created by kink on 2012-10-06T20:28:17, last modified: 2012-11-04T20:45:50

[eldering]

Trac comment by eldering on 2012-11-04 20:45:50:

Modifying the code that submissions run longer is not difficult: only changes are needed at:

• testcase_run.sh:177 increase the $((2*TIMELIMIT)) wallclock limit (which is only there the prevent submissions to sleep)
• runguard.c:410 increase the 1 second CPU limit overshoot. The real CPU time used is checked later anyways.

The question is how to present this in the jury interface: we cannot change the TIMELIMIT verdict, so currently the difference of a submission finishing before/after the overshoot limit shows through the fact that the error output mentions either one of:
.../runguard: warning: command terminated with signal 9
.../runguard: warning: timelimit exceeded (wall time): aborting command

Would we then by default always want to show differences in team/jury output?

[eldering]

FIxed in commit ef8bbeb.