You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our CI runs often run infection/infection, which is memory-intensive (unavoidable).
I think that setting a memory limit is an artificial limitation that is already well enforced by the GitHub Actions infrastructure (should we hit it): we should probably have memory_limit=-1 by default.
A memory limit enforced PHP-side doesn't give us any advantage, since it's mostly detrimental in non-web contexts anyway (and should be managed by a supervisor process anyway).
Feature Request
Summary
Our CI runs often run
infection/infection
, which is memory-intensive (unavoidable).I think that setting a memory limit is an artificial limitation that is already well enforced by the GitHub Actions infrastructure (should we hit it): we should probably have
memory_limit=-1
by default.A memory limit enforced PHP-side doesn't give us any advantage, since it's mostly detrimental in non-web contexts anyway (and should be managed by a supervisor process anyway).
Ref: laminas/automatic-releases@af78115
The text was updated successfully, but these errors were encountered: