Stability of PEAR - call to arms
| From: | Daniel O'Connor | Date: | Fri, 30 Dec 2011 06:24:50 +0000 |
| Subject: | Stability of PEAR - call to arms | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-54649@lists.php.net to get a copy of this message | ||
Hi all,
We've got
116 packages with passing tests.
135 with assorted failures.
http://test.pear.php.net:8080/ shows the current
status. If you have github
credentials and are part of the PEAR organisation, you can update config,
trigger builds, etc.
There are a few broad categories of problems & fixes:
1. A stable, PHP4 package has E_STRICT or similar failures. The most
common fix is to specify
-d error_reporting=30719 for the phpunit
command, if removing such behaviour would be a BC break
2. An unstable PHP4 package has E_STRICT/similar failures. Upgrade to
PHP 5.0.0+.
3. assertType or tests not named in a way PHPUnit 3.6 understands -
s/assertType/assertInternalType/ and rename affected tests.
There's more actual legitimate failures; but if you wanted to help the QA
team stabilise PEAR, here's where to start.
Thanks to Daniel C. we're 50% of the way there.