Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php /ext/curlinterface.c streams.c /ext/fbsql php_fbsql.c /ext/ftp ftp.c /ext/hyperwavehg_comm.c hw.c /ext/imap php_imap.c /ext/ldap ldap.c /ext/

2003-02-16 Thread Wez Furlong
Should be fixed now. If any more of these occur, the problem is that winsock2.h needs to be included before windows.h (which itself includes winsock.h). I noticed that some source files include the winsock headers twice, so there is probably some spring cleaning that can be done. I have included

[PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php /ext/curl interface.c streams.c /ext/fbsql php_fbsql.c /ext/ftp ftp.c /ext/hyperwave hg_comm.c hw.c /ext/imapphp_imap.c /ext/ldap ldap.c /ext/mcal php_mcal.c /ext/mysql php_mysql.c /ext/odbc php_odbc.c /ext/rpc/com com_wrapper.c /ext/snmp snmp.c /ext/standarddns.c file.c fsock.c ftp_fopen_wrapper.c http_fopen_wrapper.c pack.c /ext/zlibzlib.c /main fopen_wrappers.c mergesort.c network.c php.h php_open_temporary_file.cstreams.c /win32 php4dllts.dsp sendmail.c time.h

2003-02-15 Thread Sebastian Bergmann
Wez Furlong wrote: Log: A add much more useful select(2) implementation than is provided by windows sockets. This broke the build for me. I get 1500+ errors that look like this one: c:\programme\microsoft sdk\include\winsock2.h(2478): error C2375: 'WSAAsyncGetHostByName':

[PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-11-03 Thread Marcus Boerger
Maybe we should add those two settings also to the default overwrites since you can easily fail all tests by this simple settings and mbstring module as well as output buffering are checked elsewhere. marcus Index: run-tests.php ===

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-11-03 Thread Moriyoshi Koizumi
+1 Moriyoshi [EMAIL PROTECTED] (Marcus Boerger) wrote: Maybe we should add those two settings also to the default overwrites since you can easily fail all tests by this simple settings and mbstring module as well as output buffering are checked elsewhere. marcus Index: run-tests.php

[PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-11-02 Thread Marcus Boerger
You can now use php run-test.php ext/whatever At 22:48 02.11.2002, you wrote: helly Sat Nov 2 16:48:06 2002 EDT Modified files: /php4 run-tests.php Log: -allow parameters to be directories -${dir} - $dir Index: php4/run-tests.php diff -u php4/run-tests.php:1.108

[PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-29 Thread Marcus Börger
I thought we discussed that any error/warning message MUST cause a test to fail. If you look at the diffs you will see that. And that we do not use logging but direct displaying for that. And again when special tests fail because a warning is emitted you should either use --INI-- to disable

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-28 Thread Melvyn Sopacua
I guess we should add a --enable-mime-magic warning as well: PHP Warning: mime_magic: can't read magic file in Unknown on line 0 FAIL ctype on integers [ext/ctype/tests/001.phpt] PHP Warning: mime_magic: can't read magic file in Unknown on line 0 FAIL ctype on strings

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-28 Thread Marcus Börger
First of all only some tests in ext/xslt were designed to present a warning. I suggest this can be fixed by adding a --INI-- section disabling the error messages. Second i did another commit to direct logs to stderr so the errors are shown in the output. So i do not see any problem here. Third i

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-28 Thread Jani Taskinen
On Mon, 28 Oct 2002, Marcus Börger wrote: Second i did another commit to direct logs to stderr so the errors are shown in the output. So i do not see any problem here. Not necessarily..for me stderr goes to /var/log/messages, iirc. :) b) Leave it as it is now (of cause my favorite).

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-28 Thread Melvyn Sopacua
At 18:24 28-10-2002, Marcus Börger wrote: Second i did another commit to direct logs to stderr so the errors are shown in the output. So i do not see any problem here. I don't get it - display_errors=on works independantly from log_errors. Why do we need logs? [EMAIL PROTECTED] ~ $

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-28 Thread Marcus Börger
Hmm since it seems i am the only one wanting to take only the log version of the messages i think we can leave it like it is now (with log_errors=0). The reason i wanted log_errors=1 was that i simply wanted one single additional line in the .diff files whatever is configured elsewhere. marcus

[PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-27 Thread Marcus Börger
First the tests take the nomal ini settings from any file found by php... Second there are some settings overwritten by run-test.php.. Third you can overwrite first and second by specifying an INI section in the .phpt files. Now to the setting log_errors i want this thing on because ANY MESSAGE

[PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-27 Thread Ilia A.
I am curios as to your reasoning behind turning on html_errors by default, why would the tests need HTML data? Logging of errors occurred during the tests seems pointless to me. As I've mentioned before if a test needs to check if a certain type of error is generated the track_errors

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-27 Thread Melvyn Sopacua
At 01:27 28-10-2002, Ilia A. wrote: I am curios as to your reasoning behind turning on html_errors by default, why would the tests need HTML data? Logging of errors occurred during the tests seems pointless to me. As I've mentioned before if a test needs to check if a certain type of error is

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-27 Thread Jani Taskinen
+1 for removing both bogus settings. (html_errors log_errors) --Jani On Sun, 27 Oct 2002, Ilia A. wrote: I am curios as to your reasoning behind turning on html_errors by default, why would the tests need HTML data? Logging of errors occurred during the tests seems pointless to

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-27 Thread Derick Rethans
On Mon, 28 Oct 2002, Melvyn Sopacua wrote: At 01:27 28-10-2002, Ilia A. wrote: I am curios as to your reasoning behind turning on html_errors by default, why would the tests need HTML data? Logging of errors occurred during the tests seems pointless to me. As I've mentioned before if a

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-27 Thread Derick Rethans
On Mon, 28 Oct 2002, Jani Taskinen wrote: +1 for removing both bogus settings. (html_errors log_errors) Another one here then: +1 for reverting the changes. Derick On Sun, 27 Oct 2002, Ilia A. wrote: I am curios as to your reasoning behind turning on html_errors by default, why

[PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-25 Thread Marcus Börger
I haven't installed xslt yet so i do not know...but i am testing with 25% of the modules and get the feeling that we must check for all warnings and errors. A special situation is ext/session/tests/008-php4.2.3.phpt where a warning mechanism is checked..here the following would be enough

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-25 Thread Ilia A.
On October 25, 2002 04:01 pm, Marcus Börger wrote: I haven't installed xslt yet so i do not know...but i am testing with 25% of the modules and get the feeling that we must check for all warnings and errors. A special situation is ext/session/tests/008-php4.2.3.phpt where a warning mechanism

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php

2002-10-25 Thread Marcus Börger
But we are speaking about one single test. I mean multiple calls to $php_errormsg are allowed of cause. I was just looking for a solution to check whether a test produces any not wanted messages. marcus At 22:06 25.10.2002, Ilia A. wrote: On October 25, 2002 04:01 pm, Marcus Börger wrote: I