[12.x] Fix flaky test in CacheArrayStore (increment) #57905
Merged
+2
−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
This prevents timing race conditions where time can advance between when the cache value is incremented (which records a timestamp) and when subsequent time-based checks occur, causing intermittent test failures.
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.
This PR fixes a flaky test by freezing time before the increment operation in
testNonExistingKeysCanBeIncremented.Problem:
Without freezing time, there's a small window where time can advance between when the cache value is incremented (which records a timestamp) and when subsequent time-based checks occur. This can cause the test to fail intermittently.
Solution:
Add
Carbon::setTestNow(Carbon::now());before theincrement()operation to ensure consistent timing throughout the test.