What the judge's verdicts mean

The judge runs your program on the samples first, then on the hidden tests, and gives one verdict.

• Accepted: your program printed the right output on every test, within the limits.
• Wrong answer: on at least one test the output was not what was expected. Check edge cases and the exact output format the statement asks for.
• Time limit exceeded: on a test your program ran longer than the problem's time limit. Usually the method is too slow for the largest inputs, or the program waits for input that never comes.
• Memory limit exceeded: your program used more memory than the limit.
• Runtime error: your program crashed, for example by dividing by zero, reading outside an array, or recursing too deep.
• Compilation error: the code did not compile. The compiler's message tells you the line.

Tips

• Choose the same language and version you wrote the code for.
• Read the input exactly as the statement describes it, and print nothing extra, such as "Enter a number".
• When you practise on the Judge you see each sample's result, how many hidden tests passed, and the compiler's output when a build fails. In a contest you see how many tests passed, not which ones.

Sure your solution is right and the verdict is wrong? During a contest, ask in Clarifications. Otherwise open a ticket in Contests and the Judge with a link to the submission.