Barry A. Warsaw <ba...@python.org> added the comment: On Mar 23, 2011, at 04:06 PM, Antoine Pitrou wrote:
>Sorry, that's completely bogus. If a "merge race" may introduce a regression, >then there's no reason the regression will occur in the non-blacklisted >tests. Have you heard of Murphy's law? That's not the point. If it was, you'd always have to run make testall whenever you were resolving a merge race. Otherwise you could leave out something important, right? When you're in the middle of a merge race, you've *already* thoroughly tested your change, along with the full test suite, with a relatively up-to-date python tree + your changes <wink>. You've now merged any changes that have come in since you did your thorough tests, and you're trying to beat the other guy to the push. You want something that can run *fast* and just proves that the merge didn't hose Python in some brown paper bag way. It is not intended to be a thorough test since you've already done that. Anything more than a smoke test will be discovered by the buildbots. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11651> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
