Understanding Verdicts
A verdict is the result returned by the judge after you submit a solution. The short codes are standard in programming contests, so learning them will help you on other online judges too.
Common verdicts
| Code | Meaning | What to check next |
|---|---|---|
| AC | Accepted | Your solution passed all tests. Well done! |
| WA | Wrong Answer | Re-read the problem, then check edge cases, calculations, and exact output formatting. |
| TLE | Time Limit Exceeded | Your approach is too slow, or the program contains a loop that does not finish. |
| MLE | Memory Limit Exceeded | Your program stores more data than the memory limit allows. |
| CE | Compile Error | Fix the syntax or compiler errors shown on the submission page. |
| RTE | Runtime Error | Look for invalid indexing, division by zero, bad input handling, or other crashes. |
| OLE | Output Limit Exceeded | The program printed too much output, often because of an incorrect loop. |
| IE | Internal Error | The judge encountered a system problem. Tell your teacher if submitting again gives the same result. |
A useful debugging routine
- Open the submission and read its verdict.
- Test the sample input again.
- Create a small test case of your own, including boundary cases.
- Change one thing at a time and explain why the change should fix the problem.
- Submit again and compare the new result.
Getting a non-AC verdict is a normal part of programming. Treat it as feedback: the code is telling you what to investigate next.