Skip to content

fix(routine): launchd schedule test fails on Linux CI (main is red)#590

Merged
bborn merged 1 commit into
mainfrom
fix/routine-launchd-test-on-linux
Jun 11, 2026
Merged

fix(routine): launchd schedule test fails on Linux CI (main is red)#590
bborn merged 1 commit into
mainfrom
fix/routine-launchd-test-on-linux

Conversation

@bborn

@bborn bborn commented Jun 11, 2026

Copy link
Copy Markdown
Owner

Main's Test job has been red since #589: TestInstallAndRemoveLaunchdSchedule asserts the launchd backend, but interval schedules only pick launchd on darwin — on ubuntu runners it installs a cron schedule and the assertion fails.

One-line-ish fix: force osGOOS = "darwin" through the existing test seam, exactly as TestCalendarCronUsesLaunchdOnDarwin already does. Everything else in the test is already platform-stubbed (launchctl/crontab stubs, isolated dirs).

This also un-reds the merge-result CI of every open PR (e.g. #583).

🤖 Generated with Claude Code

…inux CI

Interval schedules pick the launchd backend only on darwin;
TestInstallAndRemoveLaunchdSchedule asserted Backend == launchd without
overriding osGOOS, so it installed a cron schedule on ubuntu runners and
failed (main CI is red since #589). Use the existing osGOOS test seam,
as TestCalendarCronUsesLaunchdOnDarwin already does.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@bborn bborn merged commit 31661ed into main Jun 11, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant