Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.An error occurred.
/batch?id=73&op=do
<br />
<b>Fatal error</b>: Maximum execution time of 180 seconds exceeded in <b>C:\www\webapps\drupal-6\sites\all\modules\simpletest\drupal_web_test_case.php</b> on line <b>1087</b><br />
Comments
Comment #1
nancydruI see this on the "error page":
# No test cases found.
# The tests did not successfully finish.
And I checked php.ini and the maximum_execution_time is set to 600.
Comment #2
boombatower commentedSounds like you want to fix: #447302: Cannot run Simpletest with Strict.
Comment #3
boombatower commentedComment #4
nancydruI am now using the latest -dev and this still happens.
Comment #5
boombatower commentedPlease fix #2.
Comment #6
nancydruIt looks to me like simpletest.test already has that, and this is where I am seeing this problem. I have only tried the tests that come with the module and nothing else yet.
Comment #7
boombatower commentedBased on the output from #2's issue it seems that you have a number of other modules with tests...those tests have not been updated.
My assumption is that SimpleTest is crapping (even though its own test is ok) since those are all hosed....
It really isn't usable until those modules update there tests..feel free to file patches with those modules.
Sorry, you choose an odd time to get started (during api change).
Comment #8
nancydruI didn't choose my timing - core did.
I fixed all the tests and this is still happening.
Comment #9
boombatower commentedWell otherwise I'll need to you provide some more debugging info as this obviously does not occur on my setup.
Comment #10
boombatower commentedPlease re-open if further information.
Comment #11
nancydruWhat kind of info do you want?
Comment #12
boombatower commentedOh, sry.
Core issue: #523878: Fatal error: Maximum execution time of 180 seconds exceeded