Last modified: 2011-01-31 20:37:38 UTC
Tesla does funky things getting errors were a normal setup doesn't. It should play with electricity the normal way!
I dunno... what is considered "normal" .. it fails on my setup, too.
Well, what's your setup? Which php version? 32 or 64 bits? The error happens if you do the following in the command line? php phpunit.php includes/search/SearchDbTest.php
Created attachment 7892 [details] mark's phpinfo phpinfo where this bug occurs.
SearchDbTest shows no errors, but: $ ./phpunit.php includes/ParserOptionsTest.php [.,,] Time: 1 second, Memory: 12.00Mb There was 1 error: 1) ParserOptionsTest::testGetParserCacheKeyWithDynamicDates MWException: Tried to create a ParserCache with an invalid memcached /home/mah/work/code/mediawiki/mw-svn/includes/parser/ParserCache.php:35 /home/mah/work/code/mediawiki/mw-svn/includes/parser/ParserCache.php:22 /home/mah/work/code/mediawiki/mw-svn/maintenance/tests/phpunit/includes/ParserOptionsTest.php:13 /home/mah/work/code/mediawiki/mw-svn/maintenance/tests/phpunit/phpunit.php:34
Created attachment 7893 [details] from my 64bit laptop This is from my other laptop that is also showing the same symptoms
A few differences between Tesla and average developer's setup™: * It uses install.php to setup things from CLI * On Linux, there's no predefined order in which files are returned by file search, therefore tests are run in an unpredictable order. This matters if some tests aren't isolated enough (and we have plenty of such tests, I assure you)
(In reply to comment #4) > SearchDbTest shows no errors, but: > > $ ./phpunit.php includes/ParserOptionsTest.php > [.,,] > Time: 1 second, Memory: 12.00Mb > > There was 1 error: > > 1) ParserOptionsTest::testGetParserCacheKeyWithDynamicDates > MWException: Tried to create a ParserCache with an invalid memcached Here too. Fixed in r78009. Does it help with the other issue?
(In reply to comment #6) > * It uses install.php to setup things from CLI Tried with an install.php generated LocalSettings. No change. > * On Linux, there's no predefined order in which files are returned by file > search, therefore tests are run in an unpredictable order. This matters if some > tests aren't isolated enough (and we have plenty of such tests, I assure you) Actually there usually is a sorted order due to the use of trees in the filesystem implementing the folders. r78009 seem to have fixed the tesla issues.
* On Linux, there's no predefined order in which files are returned by file search. Is this really different than the "average developer's setup™"?? Most devs I know use Linux.
fwiw, this rev (also?) helped me r78005
(In reply to comment #9) > Is this really different than the "average developer's setup™"?? Most devs I > know use Linux. It may be different on *every* Linux box, that what I meant.
