[13.x] Fix time-sensitive flaky test in NotificationDatabaseChannelTest#60333
Merged
taylorotwell merged 1 commit intoMay 31, 2026
Conversation
Member
|
Thanks! |
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.
testCustomizeTypeIsSentToDatabasechecks theread_atvalue a notificationwrites to the database. The expectation and the sent value each call
Carbon::now(), so the test fails when the two calls land on different seconds.Freezing time in
setUp()keeps them aligned.Seen on a scheduled run on my fork:
https://github.com/KentarouTakeda/laravel-framework/actions/runs/26611769748/job/78419022756
Happy to open the same fix against 12.x as well if preferred.