Submission Result Codes Explained


When you submit a solution, it will be judged and you'll receive one of the following results:

AC – Accepted

Your program passed all tests successfully. Good job!

WA – Wrong Answer

Your program ran but it produced the wrong output when compared to the expected output.

IR – Invalid Return

Your program finished with a nonzero exit code (crashed). For languages like Python or Java, this will usually include the exception name, such as NameError or java.lang.NullPointerException. Sometimes in python this means you are not taking in input correctly.

RTE – Runtime Error

This only applies to compiled languages like C or C++. It means your program crashed during execution. Common causes include:

  • Segmentation fault / Bus error: Accessed invalid memory or array out of bounds.
  • Floating point exception: Invalid math operation, like dividing by zero.
  • Killed: Program was forcefully stopped by the system (reason unknown).
  • File access: Opening files is not allowed unless specified by the problem.
  • {} syscall disallowed: Rare. Contact support if you see this.
  • std::bad_alloc: Your program failed to allocate memory (C++ only).
  • Failed initializing: Your program used too much memory at startup. Example:
    int arr[10000][10000];
    On a problem with 64MB limit, this uses ~381MB — too much.

OLE – Output Limit Exceeded

Your program printed too much output - usually over 256MB (or a custom limit for specific problems).

MLE – Memory Limit Exceeded

Your program used more memory than allowed. Sometimes this also appears as a segmentation fault or std::bad_alloc.

TLE – Time Limit Exceeded

Your program took too long to finish running. Think of a faster algorithm or optimise your code. This may indicate you have an infinite loop.

IE – Internal Error

The judge system encountered an error or the problem was misconfigured. Please submit a ticket or talk to an organiser ASAP