View Issue Details

IDProjectCategoryView StatusLast Update
0002391XdebugCode Coveragepublic2025-12-01 23:27
Reporterlaurin1 Assigned Toderick  
PrioritynormalSeveritymajorReproducibilityalways
Status assignedResolutionopen 
Product Version3.5.0alpha3 
Summary0002391: Code Coverage times out on random tests
Description

We accidentally installed 3.50-dev and then our code coverage started failing. I listed as always reproducible because if we run our entire test suite, it happens every time. However, the particular test that times out varies.

Step 3/3: PHPUnit (Command Line)
19:24:05  Starting: D:\TeamCityBuildAgent\temp\agentTmp\custom_script1165008140808374324.cmd
19:24:05  in directory: D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8
19:26:58  PHPUnit 12.4.1 by Sebastian Bergmann and contributors.
19:26:58 
19:26:58  Runtime: PHP 8.4.14 with Xdebug 3.5.0-dev
19:26:58  Configuration: D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8\phpunit\phpunit-coverage.xml
19:26:58 
19:27:03  D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8\phpunit\phpunit-coverage.xml
19:29:37 
19:29:37  Fatal error: Maximum execution time of 120 seconds exceeded in D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8\vendor\phpmailer\phpmailer\src\PHPMailer.php on line 895
19:29:37  Maximum execution time of 120 seconds exceeded<div style="background-color:#e8e8e8;height: 20px;"> </div><table id="trace">
19:29:37  <tr><td>#</td><td>File:Line</td><td>Function</td></td>
19:29:37  <tr><td>1</td><td></td><td>classes\ErrorHandling::errorHandlerShutdown::</td></tr>
19:29:37  <tr><td>2</td><td>D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8\vendor\phpmailer\phpmailer\src\PHPMailer.php:895</td><td></td></tr>
19:29:37  </table><div style="background-color:#e8e8e8;height: 20px;"> </div><table id="arguments">
19:29:37  <tr><td>#</td><td>Arguments</td></td>
19:29:37  <tr><td>1</td><td></td></tr>
19:29:37  <tr><td>2</td><td></td></tr>
19:29:37  </table>Fatal error: Premature end of PHP process when running classes\Controllers\ETL_StatusTest::test_updateETLsToRunNow_AllStaging.
19:29:37  Process exited with code 255

Steps To Reproduce

Not sure how to this can be done outside of our environment.

TagsNo tags attached.
Operating SystemWindows Server 2016
PHP Version8.4.10-8.4.19

Activities

derick

2025-12-01 23:24

administrator   ~0007419

Your tests clearly just take longer than 120 seconds of CPU time. Just... Increase the limit.

Without a reproducible case showing differences between versions, I also can't do any research about this.

laurin1

2025-12-01 23:26

reporter   ~0007420

I realize you can't research it without more info, but no, these test do not take more than 120 seconds. I switched back to the 3.4 version of Xdebug and the tests pass just fine - it's only with this specific version of Xdebug do they timeout.

laurin1

2025-12-01 23:27

reporter   ~0007421

I'll try to create a reproducible version, but as this only occurs when the entire suite is run, and all of our code is proprietary (as is the environment), that will be very difficult to do.

Issue History

Date Modified Username Field Change
2025-12-01 22:26 laurin1 New Issue
2025-12-01 23:24 derick Assigned To => derick
2025-12-01 23:24 derick Status new => feedback
2025-12-01 23:24 derick Note Added: 0007419
2025-12-01 23:26 laurin1 Note Added: 0007420
2025-12-01 23:26 laurin1 Status feedback => assigned
2025-12-01 23:27 laurin1 Note Added: 0007421