[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Autotest function usage
From: |
Paolo Bonzini |
Subject: |
Re: Autotest function usage |
Date: |
Thu, 18 Oct 2007 11:44:21 +0200 |
User-agent: |
Thunderbird 2.0.0.6 (Macintosh/20070728) |
For both patches, test time improves by ~5% for testsuite -10, and slows
down slightly for running only one test.
I like the second approach better, as the first is formally not a
complexity reduction. I'm a bit disappointed that the improvement is
not larger, though. Oh well.
I expect it to be bigger for an entire run, the same way as -10 improves
more than -1. Also, the autoconf testsuite is peculiar in that the
tests take a lot of time to run, making the sed overhead less visible.
Could we name the tests after their normalized number, i.e., 017, so
that `ls' file ordering is sane? I suppose it would be good to test
the final patch with Solaris and AIX awk (I can do so).
Would you mind doing also the former?
Should the individual test source files be deleted at the end, or even
after each one is completed? Only if -d is not given?
Probably.
If you want to get crazy, you can let awk exit after extracting the last
needed test.
No thanks. ;-)
Paolo
- Autotest function usage, Ralf Wildenhues, 2007/10/17
- Re: Autotest function usage, Eric Blake, 2007/10/17
- Re: Autotest function usage, Eric Blake, 2007/10/17
- Re: Autotest function usage, Eric Blake, 2007/10/17
- Re: Autotest function usage, Ralf Wildenhues, 2007/10/17
- Re: Autotest function usage, Paolo Bonzini, 2007/10/18
- Re: Autotest function usage, Ralf Wildenhues, 2007/10/18
- Re: Autotest function usage,
Paolo Bonzini <=
- Re: Autotest function usage, Paolo Bonzini, 2007/10/19
- Re: Autotest function usage, Ralf Wildenhues, 2007/10/21
- Re: Autotest function usage, Ralf Wildenhues, 2007/10/21