EPIJudge icon indicating copy to clipboard operation
EPIJudge copied to clipboard

Add stack trace to test failure output

Open dbedrenko opened this issue 5 years ago • 3 comments

It's frustrating to find the source of an unhandled exception in my code without having at least the line number where the problem happens.

With a full traceback debugging is made much easier.

PS: Thank you for the great book and this judge. I'm learning a lot about how to write good Python solutions!

dbedrenko avatar Sep 29 '18 11:09 dbedrenko

Hi @dbedrenko ,

I haven't dived into this very deep about how this line will affect the testing framework. Assuming this did what you mean, and I hope we could implement the same functionality for the other two languages as well (i.e., C++ and Java) because we implement judge as a whole for three parallel versions.

tsunghsienlee avatar Nov 11 '19 07:11 tsunghsienlee

@tsunghsienlee It's possible to have this for Java and I would definitely like to do so. There's a chance that we can even do it for C++ but I'll have to dig more

metopa avatar Nov 11 '19 17:11 metopa

@dbedrenko Hi there, sorry for the long wait. I'll check this out right after I do my state exams at the end of June. I'll keep you updated :)

metopa avatar Jun 07 '20 08:06 metopa