One probable reason is that some legacy tests (like 27_iosfile) produce
multiple assertion totals (or are supposed to), and we want the last of
these, rather than the first. A second possible reason was to make the
parsing FSM slightly simpler (though adding an additional character or
two to the pattern shouldn't make it much more complex). A final
possible reason was to make the parsing faster for long output files.
--Andrew Black
Martin Sebor wrote:
[...]
Why do we seek in compatibility mode instead of processing
the file from top to bottom like we normally do? There could
be any number of notes or other garbage at the end of the
output file so seeking back is never going to be reliable.
Martin
