Last modified: 2013-09-11 22:46:18 UTC
So I'm not sure whether this is affecting others, but when I try to run a suite of unit tests (e.g., "make destructive"), PHPUnit gets through a couple of tests, then it begins showing Errors on all tests, and then finally it just quits out with the "Killed" message, implying the kernel killed it for memory reasons. Output: vagrant@mediawiki-vagrant:/vagrant/mediawiki/tests/phpunit$ make safe php phpunit.php --configuration /vagrant/mediawiki/tests/phpunit/suite.xml --exclude-group Broken,ParserFuzz,Destructive,Stub PHPUnit 3.7.19 by Sebastian Bergmann. Configuration read from /vagrant/mediawiki/tests/phpunit/suite.xml ............................................................. 61 / 6525 ( 0%) ..SSSSSS.....F....EEEEEEEEE...make: *** [safe] Killed
I got further than you did (76%) but I got "Killed", too. The fact that I got further may simple be a reflection of the fact that the memory allocated to the VM by default was increased by about 200 megabytes earlier this month. (It's now at 768 Mb.) Is this just a generic issue with the tests being memory-hungry? Are they known to work on low-profile machines?
Not sure. I'm thinking it's just the tests being memory-hungry. I've tried running unit tests before on Amazon AWS micro instances (which also have limited memory) and run into the same problem.
(In reply to comment #2) > Not sure. I'm thinking it's just the tests being memory-hungry. I've tried > running unit tests before on Amazon AWS micro instances (which also have > limited memory) and run into the same problem. With 4GB of memory allocated to the VM, the tests pass. So it's just the tests being very memory hungry.
[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.]
