Run oversized bz2 resource tests in isolation to avoid OOM#22744
Merged
Conversation
gh20620 and bzdecompress_input_too_large each allocate ~4GB under RUN_RESOURCE_HEAVY_TESTS; two in parallel exhaust a memory-constrained runner and the OOM killer aborts the whole run. Mark both --CONFLICTS-- all so run-tests executes them in isolation, matching ext/tidy/tests/parsing_file_too_large.phpt.
devnexen
approved these changes
Jul 15, 2026
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
2 participants
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.
gh20620 and bzdecompress_input_too_large each allocate ~4GB under RUN_RESOURCE_HEAVY_TESTS; running both in parallel OOMs a memory-constrained runner and the killer aborts the whole run. Marking them --CONFLICTS-- all runs each in isolation, matching ext/tidy/tests/parsing_file_too_large.phpt. bzdecompress_input_too_large is master-only, so the two only coexist here.