|AC||Accepted||Your program outputted the correct answer and terminated normally.|
|WA||Wrong Answer||Your program didn't output the correct answer, but it terminated normally.|
|TLE||Time Limit Exceeded||Your program used too much CPU time or wall clock time.
The wall clock time limit is max(1.2 * TL, TL + 1s). Wall clock limit will not be triggered under normal circumstances, unless the judge server is under heavy load or your program paused by calling
|MLE||Memory Limit Exceeded||Your program used too much memory.
Program that used too much memory would not necessarily get an MLE; see Memory Accounting Types for more details.
|OLE||Output Limit Exceeded||Your program tried to extend a file (including stdout) larger than the output limit.
Note that this limit is placed on a per-file basis. There is also a limit of 2 * OL on the total output size, but this limit is enforced by setting the filesystem size and won't trigger an OLE; instead, the write operation will fail due to insufficient disk space. For example, if your program wrote too many bytes into stderr, you may get a WA because it can no longer write into stdout later.
|RE||Runtime Error||Your program terminated by exiting with a non-zero status code.|
|SIG||Runtime Error (killed by signal)||Your program was killed by a signal.
Some common causes are invalid memory access (SIGSEGV, i.e. Segmentation Fault), division by zero (SIGFPE), uncaught exceptions in C++ (SIGABRT), and invalid instruction (SIGILL). Note that SIGXFSZ is excluded since it will be interpreted as OLE.
|CE||Compilation Error||Your program failed to compile.|
|CLE||Compilation Limit Exceeded||Your program took too much time (> 60 sec) or memory (> 2 GiB) to compile.|
|ER||Judge Compilation Error||This is caused by failed compilation of the special judge program. If you see this, please contact the problem setter.|
|EE||Execution Error||These are caused by internal errors during the judging process. If you see them, please contact the site maintainer.|