RetroSearch Browse

Wed Mar 23 17:34:46 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-March/109935.html

    Barry> If I disable down to and including test_concurrent_futures,
    Barry> quicktest runs in 3m20s wall clock.  *That's* what I'm talkin'
    Barry> 'bout!

How do you know you didn't eliminate the most important tests?  (That is,
the stuff which tests the code which is currently the most flaky.)

    Barry> Any objections to adding those slowest 5 tests to the blacklist,
    Barry> and -j5 to quicktest for Python 3.3?

Convince me that you haven't so horribly skewed the coverage that the result
is no longer meaningful.

Skip

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109935.html below:

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