Course list | UNCode (2024)

After you submit your code, it will be assessed and a result will be given to you.
The tables below list all possible results.

Results related to your code. Results you may receive after assessing your code

• ACCEPTED

  Awesome! Everything worked as it should have: your code passed all the test cases. Congratulations!

• WRONG ANSWER

  Sorry, but your code failed to solve the problem. It does not solve correctly the problem you were asked for.
  The output after running your code (what it prints to the screen), is different from the output the system expected.
  If the administrator allowed it, you may be able to see the difference between your output and the expected output.
  Tips: Read carefully what you are asked to do and check again your code.
  Test your code with different inputs. You can do it in your machine or you can use the "custom input" in the tools section.

• PRESENTATION ERROR

  The data in your output is correct, but it is not formatted in the proper way. Check the problem statement to understand the correct format of the output.
  Missing/excessive blank lines or unnecessary spaces are likely to have caused this message.

  See Also

  BB Code List - Models HeavenDecoding Samsung Washer Error Codes: What Those Numbers MeanDDC EEPROM Frequently Asked Questions - EEE Parts Database | doEEEt.comBB Code List - The Settlers Online

• COMPILATION ERROR

  Your code does not compile :/. Something is faulty in your code:
  It may be a misplaced colon, bracket, quotation mark, or symbol; you may be using a reserved keyword as a variable; you may have chosen a different programming language; among other options.
  The "compilation error" message includes the output that the compiler produced with the error. Read the message carefully, it is tells you what went wrong.

• RUNTIME ERROR

  This means that your code failed while it was executing, which means that your code compiled but exited unexpectedly when executed.
  There are many reasons why your code could crashed, some of them are:
  Division by zero, invalid memory access (e.g. bad index access to an array), null pointers, among many options.

• TIME LIMIT EXCEEDED

  Your code exceeded the time limit. Thus, your code took too long to run the input for a given test case.
  There are two options: either your code got stuck in an infinite loop or your code takes much longer than it should.
  Tips: Check for infinite loops. Try to find another solution, one that takes less time to compute.

• MEMORY LIMIT EXCEEDED

  Getting this result means your code is using too much memory at runtime.
  Tips: Check the data structures you are using, or find a more "optimal" solution, a solution that uses less memory.

• OUTPUT LIMIT EXCEEDED

  Getting this result means the output of your code is longer that the allowed.
  Tips: Check for print expressions in a loop.

• GRADING RUNTIME ERROR

  Error related to notebook file submissions. This points out a runtime error while running the grading testing code.
  This might be either an error in the grading code (i.e. calling non existent variable or function) or student code (i.e. the function to be tested is not present in the notebook).
  Tips: Check that your code implements all that was requested with the correct signature.

Results related to UNCode. Unexpected errors when your code was been executed.

• INTERNAL ERROR

  If you get this message, do not worry, There's Nothing Wrong With Your Code!
  This error means UNCode had a problem while running or assessing your code. So, the problem is on our side.
  We apologise in advance. Please reload the page and try submitting again! If you still get the same result, please wait a while and try again or contact your professor.

• SUBMISSION TIMED OUT

  If you get this, it means that we had a problem running and assessing your code. Wait for a while and try to send a submission again.
  This might be also caused by a too small time limit in the task configuration (talk to your professor about it).

• OVERFLOW

  If you get this, it means the grading environment run out of memory. There might be two possible causes:

  1. The configured memory is to low to solve this problem (talk to your professor about it).
  2. Your code is printing too much data, possibly caused by prints in an infinite loop.

• ENVIRONMENT NOT
  AVAILABLE

  There was a problem while assessing your submission. Please wait a while and reload the page, and try submitting again.