2.4 Error Messages

With the advent of Cogsys v4, there is a section at the end of each output file for error messages. Before Cogsys v4, the end of the output file simply said "END", like this:

END

Now there is a section following this "END" (which is a reserved string that 'stat' recognizes, to know to stop processing) for errors. Typically, there will be no errors, and the end of the output file will look like this:

END Start of error log End of error log

Errors are put in between the 'Start' and 'End' when they occur, and are typically errors which will not cause a testlist to "error-out" in the middle of running.

The most common errors are

Missed Retrace. old: 4287, new: 4289 ...In graphics mode, each retrace is counted. If a call to %J, %K, or %L 'misses' a retrace, this is noted. Occasional occurrences of this error are OK. Ticks1: 1000: ERROR: One second took 995539804 ns ...The real-time timer counted out 1.000 seconds, but the system clock reported only .995539804 seconds passed. This error is generated if one second as measured by the hardware clock differs from the system clock by more than 4 milliseconds in 1.000 seconds. This error lets the test data analyzer know that there may be a problem with the reported response times.

The least common errors are:

Waited 501; wanted to wait 500; tickint waited 500 ...A call to #W500 yielded a wait of 501 milliseconds. If the 'Waited' time is ever greater than 1 millisecond different than the 'wanted to wait' time, this could indicate trouble with the computer's hardware. input: key time 438 <> ticks 439 ...A call to #R reported 438 milliseconds to press a key, but the 'check' of the timer reported 439 milliseconds. This error rarely, if ever, occurrs.