> > There are still a significant number of tests which fail, > > because they are not supposed to run in a CLI context. > > > > For example > > > > $ cat ext/session/tests/001.out > > > > Warning: Cannot send session cookie - headers already sent in /lrg/php4/ext/session/tests/phpt.z2gONf on line 15 > > > > Warning: Cannot send session cache limiter - headers already sent (output started at /lrg/php4/ext/session/tests/phpt.z2gONf:15) in /lrg/php4/ext/session/tests/phpt.z2gONf on line 15 > > Yup, I know this. I already fixed some of it, but didn't have time to > check everything yet. > > BTW... I'm wondering why this error pops up. Edin, does the CLI use the > 'normal' CGI -q option?
Yes it does which means that it also tells PHP that the headers have already been sent to prevent printing them. Therefore functions that output headers will not work with the CLI. For some tests the warning can be supressed, some others just don't make sense with CLI (post/get tests, etc). We should probably skip tests that require specific SAPI and run them with CGI if available. PHP_SAPI constant can be used to distinguish the two. I guess that merging "make test" fixes in PHP_4_2_0 is OK. Edin -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
