Hi,
*Br. Anand Shenoi anandam@outlook.com [15/12/19]:
Is there any output limit hardcoded in DOMJudge? What could be the reason why the global output limit is not being taken by the system?
no, there is no output limit next to the global and problem specific settings.
For further debugging, you may add debug output to the testcase_run.sh script, e.g. here: https://github.com/DOMjudge/domjudge/blob/5.0/judge/testcase_run.sh#L192
Add something like: logmsg $LOG_INFO "file size limit is $FILELIMIT"
and judge the submission twice (once with problem specific output limit, once without).
Please send us the *full* judgedaemon log of these judgings as well as the file sizes of *every* file in the testcaseXXX directory of these judgings.
Thanks, Tobi
The issue we see is with the output limit till 13 mb, it working i.e, it is giving the expected result - TLE.
Beyond that it crashes the judge host. It doesn't give TLE also. I am attaching the test case that creates the problem. My colleague Sunil will send you the log.
________________________________________ From: Tobias Werth tobias.werth@fau.de Sent: Saturday, December 19, 2015 5:32 PM To: Br. Anand Shenoi Cc: Jaap Eldering; Thijs Kinkhorst; domjudge-devel@domjudge.org Subject: Re: Output limit
Hi,
*Br. Anand Shenoi anandam@outlook.com [15/12/19]:
Is there any output limit hardcoded in DOMJudge? What could be the reason why the global output limit is not being taken by the system?
no, there is no output limit next to the global and problem specific settings.
For further debugging, you may add debug output to the testcase_run.sh script, e.g. here: https://github.com/DOMjudge/domjudge/blob/5.0/judge/testcase_run.sh#L192
Add something like: logmsg $LOG_INFO "file size limit is $FILELIMIT"
and judge the submission twice (once with problem specific output limit, once without).
Please send us the *full* judgedaemon log of these judgings as well as the file sizes of *every* file in the testcaseXXX directory of these judgings.
Thanks, Tobi