make recheck?
Diego Novillo
dnovillo@google.com
Sat Oct 2 16:44:00 GMT 2010
On Sat, Oct 2, 2010 at 05:54, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
> Asking because it could help speed up patch development:
> 1) hack hack hack
> 2) make -k check-$whatever
> 3) go back to (1) until satisfactory
> 4) git commit patch, undo patch in work tree, rebuild
> 5) run 'make recheck' to ensure all new failures were already old.
This sounds like a great idea. You'd need to extract the FAIL lines
from the .log file and backtrack to figure out which .exp file
produced them. This would give you the input for
RUNTESTFLAGS=f.exp=...
I don't recall if you can specify more than one file in the
RUNTESTFLAGS argument, though.
Diego.
More information about the Gcc
mailing list