hi, Right, I sadly did not run them as I use to between the last RC and final but only the apps tests (wp&co), which do not use crypt's md5. I also agree about the amount of failing tests and warnings, for the same reasons. However checking the delta between two releases should help too (that's what I use to stop a release).
btw, can we go with 5.3.8 instead? I really don't like the pl thing :) Cheers, On Sat, Aug 20, 2011 at 2:09 AM, Stas Malyshev <smalys...@sugarcrm.com> wrote: > Hi! > > On 8/19/11 5:02 PM, Rasmus Lerdorf wrote: >> >> The secondary problem is that we are not doing a good job running our >> tests prior to releases. I think this is mostly because we have way too >> many tests that fail and one more or less failing test gets lost in the >> noise. > > Yes, this is a problem: here > http://gcov.php.net/viewer.php?version=PHP_5_4&func=tests we have 218 > failing tests. Unit test system with this amount of failures is next to > useless. So if we have some component that is buggy (like DateTime) or not > updated - we need to figure out a way to separate tests that we know would > fail (XFAIL?) from tests that should not fail and not release a version > until the second number is 0. Otherwise we get broken releases. > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
