On Jul 17, 2014, at 11:47 PM, Matthew Fortune <matthew.fort...@imgtec.com> wrote: > Thanks for fixing this. I'm afraid I managed to get confused between > failures we had seen sporadically in our development work and thought > they were known regressions on trunk waiting to be fixed when actually > we were introducing them.
I recommend contrib/compare_tests for checking for regressions. It tells you just what you need to know, and if they first line is unimportant, you’re done reading. If the first three lines are interesting, then you have at least 1 regression left. By reducing the line count of what you have to look at, it making it exceedingly hard to ignore it and exceedingly hard to accidentally put in a regression.
