Wall Time Limit Exceeded
When the program under test is running, it is possible that the program does not consume processor time. For example, the program is trying to read input from standard input instead of reading from a file, or it makes some system call like sleep. In this case, the limit on processor time does not allow to kill the process in a reasonable astronomical time.
Different testing systems solve this problem in different ways. In the ejudge system, the problem is solved by limiting the maximum astronomical time (see astronomical time) for the program to work (see max_real_time_limit). It is recommended to set the astronomical time limit several times larger than the CPU time limit. If the astronomical time limit is exceeded, the program under test is also removed from execution with this diagnostic.