Closed baziorek closed 6 years ago
How did you add the problem? Per zip upload or through the web interface? Or directly in the DB?
Also which DOMjudge version do you use?
I've just commited a1e0ea7543ca3bd33d8fbfa4101e7c9ee4c5c619 for the master branch.
@meisterT I'm using 6.0.1 version. I was adding this normally through web administrator's interface:
Ok, this should now be fixed both in master and 6.0 branch. Thanks for reporting! I've also added a check in the judgedaemon to create an internal error.
Thanks for fast fix:).
Description of the problem / feature request
I've not added output file to testcase -it was just warning, but judgehost is crashing, so I suggest to replace it with error or to handle that situations in judgehosts. What is more in list of testcases not-existing file has it's own hash -so it is hard to find (if somebody forgot)
Your environment