PHP Fatal error: Maximum execution time of 1 second exceeded

[HumbleBeck]

Summary of a problem or a feature request

Hello, I'm running ./vendor/bin/phpstan analyse app --memory-limit=256M on my Laraval project, and it's crashing with an error "PHP Fatal error: Maximum execution time of 1 second exceeded", increasing memory limit not helping.

Expected output

List of errors in the code.

[ondrejmirtes]

It's not about memory limit, it's about max_execution_time, you should set it to -1 for PHP CLI.

[HumbleBeck]

php -i | grep max_execution_time
max_execution_time => 0 => 0

Still same issue

[ondrejmirtes]

What does var_dump(ini_get('max_execution_time')); say if you put it to vendor/bin/phpstan?

[HumbleBeck]

string(1) "0"

[ondrejmirtes]

One more idea - try to comment this in vendor/bin/phpstan:

$xdebug = new XdebugHandler('phpstan', '--ansi');
$xdebug->check();
unset($xdebug);

[HumbleBeck]

Still the same

[HumbleBeck]

Each time it's going till 67/68 % then throwing an error

[ondrejmirtes]

Oh, I get it now. You have set_time_limit somewhere in your analysed code and it gets executed. Remove the line from there. Run PHPStan with --debug to find out which file.

On Tue, 3 Jul 2018 at 11:09, Bohdan Stadnyk ***@***.***> wrote: Each time it's going till 67/68 % then throwing an error — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1145 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGZuBoaSnTQmyAndVvmys-nsw9RJ3DBks5uCzS3gaJpZM4U_jMt> .

-- Ondřej Mirtes

[ondrejmirtes]

It happens only when you autoload file with a class declaration and the line is there - so it can happen in your application too when you ask for the same class...

On Tue, 3 Jul 2018 at 11:12, Ondřej Mirtes ***@***.***> wrote: Oh, I get it now. You have set_time_limit somewhere in your analysed code and it gets executed. Remove the line from there. Run PHPStan with --debug to find out which file. On Tue, 3 Jul 2018 at 11:09, Bohdan Stadnyk ***@***.***> wrote: > Each time it's going till 67/68 % then throwing an error > > — > You are receiving this because you modified the open/close state. > > > Reply to this email directly, view it on GitHub > <#1145 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAGZuBoaSnTQmyAndVvmys-nsw9RJ3DBks5uCzS3gaJpZM4U_jMt> > . > -- Ondřej Mirtes

-- Ondřej Mirtes

[HumbleBeck]

That was the case, thanks a lot, and sorry for bothering you

[ondrejmirtes]

Fine 😊 In the future, this will no longer be an issue when running the analysis.