Skip to content

fix: raise memory_limit in release.sh test invocation#108

Merged
markshust merged 1 commit into
developfrom
feature/release-script-memory-limit
Jun 3, 2026
Merged

fix: raise memory_limit in release.sh test invocation#108
markshust merged 1 commit into
developfrom
feature/release-script-memory-limit

Conversation

@markshust
Copy link
Copy Markdown
Collaborator

Summary

  • bin/release.sh invokes pest directly (not through composer test) to include the integration-destructive group, so the memory_limit fix from fix: raise memory_limit in composer test scripts #107 didn't apply here.
  • Default PHP CLI memory_limit=128M is exhausted during paratest's parallel suite loader, killing the release before any test runs.
  • Mirror the composer-script fix by passing -d memory_limit=2G to the pest invocation in the release script.

Test plan

  • ./bin/release.sh <version> reaches the test phase without "Allowed memory size … exhausted".

🤖 Generated with Claude Code

bin/release.sh runs pest directly (not via `composer test`) to include
the integration-destructive group, so it didn't pick up the
memory_limit bump from #107. Default PHP CLI memory_limit (128M) is
exhausted during paratest's parallel suite loader, aborting the
release before any test runs. Mirror the composer-script fix by
passing `-d memory_limit=2G` to the pest invocation here as well.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@markshust markshust merged commit 0f8e9c8 into develop Jun 3, 2026
@markshust markshust deleted the feature/release-script-memory-limit branch June 3, 2026 14:22
@github-actions github-actions Bot added the bug Something isn't working label Jun 3, 2026
michalbiarda pushed a commit to michalbiarda/marko that referenced this pull request Jun 4, 2026
IntegrationVerificationTest spawns pest as a subprocess (via exec) to
verify the suite still runs after a destructive composer reinstall and
to assert no fatal PHP errors surface in the output. Those subprocesses
inherit the default CLI memory_limit (128M), so paratest's parallel
suite loader exhausts memory mid-run — which the assertion at
tests/IntegrationVerificationTest.php:171 then catches as a "PHP Fatal
error" in the captured output, failing the release.

Pass `-d memory_limit=2G` to both pest invocations (lines 109 and 162),
mirroring the fix in marko-php#107 / marko-php#108.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant