Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
simpletest.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Sep 2008 at 09:21 UTC
Updated:
9 Jul 2009 at 00:27 UTC
Jump to comment: Most recent file

Comments
Comment #1
webchickDo you get that from the outset? I'm getting a timeout error on #296310: TestingParty08: drupal_http_request redirects need a test when I run that particular test, but the rest pass for me.
Comment #2
catchThis has popped up a few times, I also had to increase max_execution_time on my laptop. See http://groups.drupal.org/node/11993#comment-43068 for another example.
Comment #3
cwgordon7 commentedYou need to increase maximum php execution time, especially on slower machines.
Comment #4
damien tournoud commentedI would like we dig into this one further. If I remember correctly, we had a
set_time_limit(0)somewhere in the code, but we lost it somehow.Comment #5
catchRetitling, would be good to fix this, or at a minimum add a hook_requirements() for it.
Comment #6
boombatower commentedHow about we get #295697: Increase PHP Memory Limit for Simpletest in first since these are related.
Comment #7
damien tournoud commentedComment #8
pwolanin commentedComment #9
webchickLet's get a hook_requirements() in there, please.
Comment #10
damien tournoud commentedOk, this should do it.
Comment #11
damien tournoud commentedComment #12
damien tournoud commentedOups, negated a condition.
Comment #13
pwolanin commentedhmm, still problematic I think - on a host with a long max execution time but where the client is not allowed to call set_time_limit() simpletest will install, but still throw errors. Can you use init_set() instead?
Comment #14
boombatower commentedComment #15
dries commentedBTW, increasing the max_execution_time fixed this problem for me.
Comment #16
dries commentedMy problem might not have been detected by this patch. I had xdebug turned on with excessive profiling and logging to files. This slowed down Simpletest by a factor X causing the above error to happen. I can try to reproduce that setup to see if this solves the problem.
Comment #17
webchickDries: Also be careful of xdebug spitting stuff out into the browser. Batch API dies horribly if there are headers printed before it thinks they ought to be printed, it seems.
I have seen this error cause problems for other people (poor pwolanin was ripping his hair out the other night because he was getting intermittent failures in the db tests because of this), so it's still worth fixing this issue.
Comment #18
Anonymous (not verified) commentedThe last submitted patch failed testing.
Comment #19
BartVB commentedBumped into this bug when trying out SimpleTest, patch seems to work but doesn't solve my problem. I get:
An HTTP error 0 occurred.
/drupal/?q=batch&id=10&op=do
which seems to be some sort of HTTP timeout and not an execution time problem. When I get the message the test is still running.
Rerolled to patch to make testing.drupal.org happy :)
Comment #20
boombatower commentedWe have max execution code in SimpleTest, believe that fixes this.