From 312be65417844677030f03f4d8e50a6b82352d9a Mon Sep 17 00:00:00 2001 From: Martin Polanka Date: Mon, 16 Oct 2017 19:12:24 +0200 Subject: [PATCH] exit code mappings --- FAQ.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/FAQ.md b/FAQ.md index bc44510..80779ca 100644 --- a/FAQ.md +++ b/FAQ.md @@ -26,3 +26,7 @@ This feature is currently not supported directly. If need be, we can create the Before we start let us define debug vs. regular submissions. The results of a debug submission contain evaluation results, the execution log and the outputs of executed programs. And the results of a regular submission contain only the results needed for proper assignment of points (aka. evaluation results). With this being said, all submissions made by students for an assignment are regular and even submissions of reference exercise solutions are regular. As a supervisor you should be able to do something called resubmitting a user solution; this feature should be available on every page of a particular submission. On resubmitting, debug outputs and execution log are turned on by default and can be found in the results archive. Please note that resubmitting all solutions for an assignment is just a regular submission without debug information. + +## Exit Codes + +For some particular languages ReCodEx provides mappings of exit codes from internal runners to messages. Full tables of codes can be found on [separate page](https://github.com/ReCodEx/wiki/wiki/Exit-Code-Mappings). \ No newline at end of file