On a fresh install of drupal 7.14, I enabled the Testing module and attempted to run the tests for the Block module. A few seconds after seeing the batch progress bar appear, I am presented with a screen saying "An error has occurred." The error in red starts with "An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows." and is followed by a large block of text that appears to be a few concatenated HTML pages followed by some AJAX. The same thing seems to happen when running the tests for other modules as well.

I've sanitized the raw response from the last request to batch and saved it at http://pastebin.com/4P3xzApk

Comments

realityloop’s picture

realityloop commented

Have run across this as well, we think it may be a php bug, what version of php are you using?

https://bugs.php.net/bug.php?id=62547

Jooblay.net’s picture

Jooblay.net commented

We are having this issue as well and causes tests to fail in the testing module from core Drupal 7.14 On the php5 we are running php 5.2.17:)

realityloop’s picture

realityloop commented

@lesseen

Can you tell me anything about the setup of the machine you are running tests on?

OS win/mac/*nix
Apache/nginx
Aegir? v1.x or 2.x
Database mysql/mariadb/other

We're using php 5.3.14/15 and it's happening on both for us

realityloop’s picture

realityloop commented

This will likley solve your issue

http://drupal.org/node/1671200#comment-6288204

Jooblay.net’s picture

Jooblay.net commented

Yes I, we are running a vps with apache2, mysql and php 5.2.17. as for the patch because none of our sites are actually broken at all and this error only shows in testing we do not apply patches due to larger issues that can arise:( As the saying goes if it aint broke, dont fix it:)

Apache2: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_fcgid/2.3.6

Server API CGI/FastCGI

Mysql: Client API version 5.0.95

PHP5: version 5.2.17

It does look like people are having success applying the above patch:) http://drupal.org/node/1671200#comment-6288204

Thanks for more information on this, and we will wait for another update. Is this new patch in Drupal 7.15? Thanks again,

spam38’s picture

spam38 commented
Version: 7.14 » 7.15

I was originally using PHP 5.4.5, but it seems broken in 5.3.15 as well. The good news is that http://drupal.org/node/1671200#comment-6288204 does indeed fix things.

realityloop’s picture

realityloop commented

yes I can confirm it is broken in 5.3.14-15 and 5.4.3-5 without the patch

mile23’s picture

mile23
Primary language English
Location Seattle, WA
commented
Version: 7.15 » 7.17

Same problem in 7.17 and PHP 5.4.4. No problem in PHP 5.2.17.

Version: 7.17 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.