Home Original page

[Python-Dev] Trimming the fat from "make quicktest" (was Re: I am now lost

[Python-Dev] Trimming the fat from "make quicktest" (was Re: I am now lost - committed, pulled, merged, what is "collapse"?)

Antoine Pitrou solipsis at pitrou.net
Wed Mar 23 14:31:23 CET 2011 
On Wed, 23 Mar 2011 22:49:39 +1000
Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Wed, Mar 23, 2011 at 9:45 PM, John Arbash Meinel
> <john at arbash-meinel.com> wrote:
> > I don't specifically know what is in those 340 tests, but 18min/340 =
> > 3.2s for each test. Which is *much* longer than simple smoke tests would
> > have to be.
> 
> The counts Barry is referring to there are actually counting test
> *files*, rather than individual tests. We only have 359 of those in
> total though (not counting those in subdirectories), so a "quicktest"
> that omits less than 6% of them doesn't sound particularly quick (even
> if it does leave out the slowest ones).
> 
> We should probably do another pass and add a few more tests to the
> blacklist in the Makefile template (starting with
> test_concurrent_futures).

Does anyone use "make quicktest" for something useful?
There is a reason the regression test suite has many tests...
"Blacklisting" some of them sounds like a bad thing to do.

Regards

Antoine.
More information about the Python-Dev mailing list