Skip to content

Fix the Laravel Cloud timer cap test on main and add #1024 to the 2.23.0 notes - #1081

Merged
rmcdaniel merged 1 commit into
mainfrom
workflow/fix-cloud-timer-test
Nov 11, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
workflow/fix-cloud-timer-test

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Main's build failed after #1074: coverage-unit reported TimersTest::testTimerCapsDelayForLaravelCloudDriver with "-900.0 is equal to 899 or greater" (run 43041146489). The test came from the 1.x PR (#1072), where Carbon 2's diffInSeconds is unsigned. On main, Carbon 3's is signed, and the test measured from the wrong end. The product code is correct. The existing SQS test on main already uses $now->diffInSeconds($job->delay), and this aligns the Cloud test with it. PR CI doesn't run this file, so only main caught it.

This also adds #1076 (#1024 fix, merged after the release metadata) to the 2.23.0 CHANGELOG section, so the 2.23.0 tag can go on this green main commit.

🤖 Generated with Claude Code

…e 2.23.0 notes

Carbon 3's diffInSeconds is signed. The test copied from 1.x measured the
delay from the wrong end and saw -900, failing main's coverage-unit job.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel
rmcdaniel merged commit d5169dd into main Nov 11, 2026
24 checks passed
@rmcdaniel
rmcdaniel deleted the workflow/fix-cloud-timer-test branch November 11, 2026 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant