fix: raise memory_limit in IntegrationVerificationTest pest subprocesses#109
Merged
Merged
Conversation
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 #107 / #108. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
IntegrationVerificationTestspawns pest as a subprocess viaexec()to verify the suite still runs after a destructivecomposer updateand to assert the captured output contains no fatal PHP errors.memory_limit=128M, so paratest's parallel suite loader ran out of memory mid-run. Thenot->toContain('PHP Fatal error')assertion attests/IntegrationVerificationTest.php:171then failed the release.-d memory_limit=2Gto both pest invocations (lines 109 and 162), completing the trio with fix: raise memory_limit in composer test scripts #107 (composer scripts) and fix: raise memory_limit in release.sh test invocation #108 (release.sh).Test plan
php -d memory_limit=2G vendor/bin/pest --filter "runs the full test suite and all tests pass"→ passes in ~6s../bin/release.sh <version>clears the test gate.🤖 Generated with Claude Code