Edit report at https://bugs.php.net/bug.php?id=61481&edit=1
ID: 61481 Patch added by: mattfic...@php.net Reported by: mattfic...@php.net Summary: Test Bug - ext/com_dotnet/tests/bug49192 Status: Open Type: Bug Package: Testing related Operating System: Windows PHP Version: 5.3.10 Block user comment: N Private report: N New Comment: The following patch has been added/updated: Patch Name: bug49192 Revision: 1332450831 URL: https://bugs.php.net/patch-display.php?bug=61481&patch=bug49192&revision=1332450831 Previous Comments: ------------------------------------------------------------------------ [2012-03-22 21:13:29] mattfic...@php.net Description: ------------ Expected result: ---------------- test pass Actual result: -------------- test fail 001+ Fatal error: Uncaught exception 'com_exception' with message 'Failed to create COM object `ADODB.Connection': The specified module could not be found. 001- int(0) 002+ ' in C:\php-sdk\php-5.3-src-r324324\ext\com_dotnet\tests\bug49192.php:15 003+ Stack trace: 004+ #0 C:\php-sdk\php-5.3-src-r324324\ext\com_dotnet\tests\bug49192.php(15): com->com('ADODB.Connectio...') 005+ #1 {main} 006+ thrown in C:\php-sdk\php-5.3-src-r324324\ext\com_dotnet\tests\bug49192.php on line 15 This test fails to load ADO (using COM). The patch marks it as XFAIL and provides this info. A change in windows longhorn x64(affecting vista, 7, 8, 2008, 2008r2) broke ADO. There is a fix available, but user has to install it. Given that ADO was deprecated a long time ago in favor of newer APIs, I don't think its worth the trouble of making the user install the fix to get an accurate test run. its better to just not run the test or expect it to fail. see: http://support.microsoft.com/kb/2517589 see: http://www.infoq.com/news/2011/10/ADO-Win7 ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=61481&edit=1
