Use the correct lock constant when stream wrapper locks the file #16
Conversation
This file contains 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
$operation contains `0` value which results to `ValueError: flock(): Argument #2 ($operation) must be one of LOCK_SH, LOCK_EX, or LOCK_UN` So we explicitly use `LOCK_SH`
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.
$operation contains
0value which results toValueError: flock(): Argument #2 ($operation) must be one of LOCK_SH, LOCK_EX, or LOCK_UNSo we explicitly use
LOCK_SHFixes failed builds for infection/infection#1549
Background:
PHPUnit sets an exclusive lock when flushed results into
.phpunit.result.cachefile, herehttps://github.com/sebastianbergmann/phpunit/blob/83ff29a80f63b8354be60e057c1dad37cc04570b/src/Runner/DefaultTestResultCache.php#L144
and our stream wrapper was not ready for it - it failed with the error above.