[Python-Dev] I am now lost - committed, pulled, merged, what is "collapse"?
Barry Warsaw
barry at python.org
Tue Mar 22 23:05:39 CET 2011
On Mar 23, 2011, at 07:31 AM, Nick Coghlan wrote:
>On Wed, Mar 23, 2011 at 4:25 AM, Barry Warsaw <barry at python.org> wrote:
>> It probably wouldn't be a bad idea to add a very fast "smoke test" for the
>> case where you get tripped up on the merge dance floor. When that happens,
>> you could run your localized tests, and then a set of tests that run in just a
>> minute or two.
>
>What would such a smoke test cover, though? It's hard to think of
>anything particularly useful in the middle ground between "Can you run
>regrtest *at all*?" and "make quicktest".
make quicktest runs 340 tests, and I'm certain many don't need to be run in a
smoke test. E.g.
test_aifc
test_colorsys
test_concurrent_futures
(that's as far as it's gotten so far ;)
Or you could time each individual test, choose a cut off for total test run
and then run whatever you can within that time (on some reference machine).
Or maybe just remove the longest running 50% of the quick tests.
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20110322/8322ed4d/attachment.pgp>
More information about the Python-Dev
mailing list