You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@niknetniko Thanks for solving the underlying issue of not properly reporting the "memory limit exceeded" case.
I still believe Dodona should have a better way to report test cases and contexts that have not been executed and evaluated by the judge due to some critical event (e.g. an exceeded time or memory limit in earlier contexts/test cases).
Using the more granular status (correct, wrong, runtime error, time limit exceeded, memory limit exceeded) instead of the binary status (correct/wrong) in rendering the feedback could improve the interpretability for the students by better explaining why something went wrong. We could use different color codes and different icons to make this differentiation, and extend the more granular status with an additional "not executed/evaluated" status.
Bonus: If no output (in the above case return value) is generated, we could avoid that Dodona puts effort in diffing the expected/generated output.
Submission: 13852943
Not clear for student what this message means, and what causes the message.
If I run the first test case locally, this is the stack trace of the exception that is raised
so student should get to see this message as feedback.
The text was updated successfully, but these errors were encountered: