As seen in the log at http://qa.drupal.org/pifr/test/130769, Drupal Commerce tests on the 7.x-1.x branch itself and any patch that gets sent for testing all fail before ever running a single test. The testbot hits the memory limit of 256M and brings things to a halt. However, just a week ago (the last time tests were run), things went swimmingly. There have been no new releases of any of our dependencies since then, and tests still function properly locally in a comparable setup.

Comments

rfay’s picture

Working through this with @rszrama, we noted that the same result happens on multiple testbots. I have provided a download of the actual code checked out by the testbot to @rszrama.

rfay’s picture

Status: Active » Fixed

I ran this test locally with the code provided to Ryan and just ran the "Drupal Commerce" tests using the web UI on MacOS with MAMP. It immediately failed with out of memory, Allowed memory size of 268435456 bytes exhausted (tried to allocate 32 bytes)

A simple way to set this up is just to add

ini_set('memory_limit', '256M');

to your settings.php.

Since it looks to me like this is a Commerce/Dependencies problem and is easily recreatable even in a Mac environment, I'm marking this fixed; Doesn't mean it's not a problem, just that it's not the testbot's fault.

rszrama’s picture

Any further clues on where to look then? As stated above, between the last time the tests were working and the time they're now failing, literally nothing had changed in either Commerce itself or our dependencies. Does the testbot use Drupal 7.x-dev or the latest tagged release? That's the only possible difference I can see, and I can ensure through the admin report on Drupal that I'm running tests at 256M - I updated php.ini directly and the report shows as much.

rfay’s picture

You'll have to use devel's page memory usage and similar performance tools. You have to code that the testbot is using, and the problem is recreatable with that code.

rfay’s picture

I've put another version of the checked-out code in https://www.dropbox.com/s/glx7qdfpfwrh1om/commerce_checkout.20120711.tgz

Please try your test with that. This one doesn't depend on the git cache.

You can use git describe --all to see what version of code is checked out.

You can use git bisect to see if the problem does not happen in an earlier version of Commerce.

rfay’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.