Re: PEAR 1.9 release
| From: | Helgi Þormar Þorbjörnsson | Date: | Wed, 12 Aug 2009 11:12:01 +0000 |
| Subject: | Re: PEAR 1.9 release | ||
| References: | 1 2 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-5417@lists.php.net to get a copy of this message | ||
On Wed, Aug 12, 2009 at 1:17 AM, Chuck Burgess<demon.gene@gmail.com> wrote:
> 2009/8/11 Helgi Þormar Þorbjörnsson <helgith@gmail.com>
>
>> Hi guys,
>>
>> Here's a pre RC1 release for you guys to test. I would like to do a
>> stable release very soon so we can slip into 5.2.11 and 5.3.2 without
>> a problem.
>>
>>
>> http://pear.php.net/~helgi/PEAR-1.9.0RC1.tgz<http://pear.php.net/%7Ehelgi/PEAR-1.9.0RC1.tgz>
>> Along with some yummy phar files.
>>
>>
>> http://pear.php.net/~helgi/go-pear.phar<http://pear.php.net/%7Ehelgi/go-pear.phar>
>>
>> http://pear.php.net/~helgi/install-pear-nozlib.phar<http://pear.php.net/%7Ehelgi/install-pear-nozlib.phar>
>>
>> Please test them all for me as we has some fun problems with the phar
>> files packaged in 5.2.10 - Apparently no one gave it proper spin
>> around and testing before it got put into the PHP release.
>>
>> A good way to test that behaviour is dropping install-pear-nozlib.phar
>> into the /pear folder of a extracted PHP tgz file and run make install
>> and see what happens. Same can be done with a checkout of PHP.
>> I would like to see testing on PHP 4.4, 5.1.6, 5.2.10 and 5.2 trunk,
>> 5.3.1 and 5.3.0 and 5.3 trunk if possible
>>
>> CC'ed Jan in since he's the only PHP 4.4 person I know :-)
>>
>> I gave this whole thing a spin my self with our testing facilities on
>> 4.4 5.2 and 5.3 and there is only bug10092-* failing if you don't have
>> CGI around (need to make that skip one of these days, I will, I
>> promise).
>>
>> Regards
>> Helgi
>>
>
>
>
> Helgi,
>
> Here are my 4.4.9 results:
>
> TOTAL TIME: 01:46
> 669 PASSED TESTS
> 22 SKIPPED TESTS
> 11 FAILED TESTS:
>
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_Command_Install/upgrade/test_bug16046.phpt
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_Command_Remote/list-upgrades/test.phpt
>
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_Common/test_infoFromString_invalidxml.phpt
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_Downloader/test_upgrade_pear_to_pecl.phpt
>
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_Downloader_Package/test_initialize_invalidpackagexml.phpt
>
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_Installer/test_install_cfgrole_upgrade.phpt
>
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_Installer/test_install_simplelocalpackage_BC.phpt
>
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_PackageFile_Generator_v2/toPackageFile/test_phprelease1.phpt
>
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_PackageFile_Generator_v2/toTgz2/test_extbin.phpt
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_Registry/api1_1/test_hasWriteAccess.phpt
> /opt/work/puc/projects/pear-core/pear-core/tests/PEAR_RunTest/bug10286.phpt
>
> I was going to try running a *baseline* against 1.8.1, but I think that
> parse error in the v2.php file is the reason for most of the 54 test
> failures I see there. I can't run at all against 1.8.0 due to a different
> file with a parse error.
>
> Let me know if any of these failures are not ones you know about or expect,
> and I'll pastebin diffs for them.
> --
> CRB
>
Which v2.php file exactly and what error? None of my lint tools detect it.
- Helgi