This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients barry, ncoghlan, pitrou
Date 2011-03-23.15:31:30
SpamBayes Score 1.6968211e-06
Marked as misclassified No
Message-id <20110323113125.0a74f078@neurotica.wooz.org>
In-reply-to <1300893282.3495.16.camel@localhost.localdomain>
Content
On Mar 23, 2011, at 03:14 PM, Antoine Pitrou wrote:

>> test_mmap
>> test_shelve
>> test_posix
>> test_largefile
>> test_concurrent_futures
>
>Why would you blacklist these tests? They are useful.

Please keep in mind the use case.  Are these really necessary in a push-race,
post-local-merge, does Python crash-and-burn case?

>I agree with Skip's latest message on python-dev: if you blacklist
>things you are removing some coverage.

Of course, but everyone who develops Python should understand when to run the
appropriate test target <wink>.

>In the patch I've removed -l, which I've never seen do anything useful.

+1.  I think -j is more useful than -l.

-Barry
History
Date User Action Args
2011-03-23 15:31:31barrysetrecipients: + barry, ncoghlan, pitrou
2011-03-23 15:31:31barrylinkissue11651 messages
2011-03-23 15:31:31barrycreate