Emit warning when OPCache is enabled while collecting coverage #6299
+169
−0
Conversation
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
staabm
commented
Aug 8, 2025
sebastianbergmann
added
type/enhancement
staabm
force-pushed
the
opc
branch
5 times, most recently
from
27511be to
ae7c73e
Compare
|
@sebastianbergmann any tips on how to run this test properly in the phar tests? locally it works for me, but CI errors |
Short answer: don't. I do not see anything here that would be specific to the PHAR. A regular PHPT test should be all that we need here. Does that help? |
we don't currently run regular tests with opcache + coverage-driver, therefore I cannot make the new test in CI fail. |
Prevents "Warning: JIT is incompatible with third party extensions that override zend_execute_ex(). JIT disabled. in Unknown on line 0"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
because of byte-code optimizations results of coverage collection can be wrong, as the source beeing executed might no longer match the actual php script sources
closes sebastianbergmann/php-code-coverage#1022