Skip to content

cli: stop calendar slots tests from expiring with the calendar - #483

Merged
alexeygrigorev merged 1 commit into
mainfrom
fix-calendar-slots-date-rot
Nov 18, 2026
Merged

alexeygrigorev merged 1 commit into
mainfrom
fix-calendar-slots-date-rot

Conversation

@alexeygrigorev

Copy link
Copy Markdown
Member

Validate CLI went red on main (run 44325713741, 5 failures, all in cli/test/calendar.test.mjs) purely because the clock reached 2026-11-18: the calendar slots availability summary intentionally starts at today (futureWeekdays), and the tests hardcoded then-future 2026-11-17/24 dates that fell out of the summary. Move the fixtures to stable future weekdays (2030-01-14/15/22) so the expectations cannot age out again. Pre-existing failure, no product code touched.

The slots availability summary starts at today (futureWeekdays), so the
tests hardcoded 2026-11-17 dates that silently fell out of the summary
once the real clock passed them; Validate CLI has been red on main since
Nov 18 for that reason alone. Move the fixtures to stable future
weekdays (2030-01-14/15/22, Mon-Tue) so the expectations no longer age
out.
@alexeygrigorev
alexeygrigorev merged commit c0b0435 into main Nov 18, 2026
1 check passed
@alexeygrigorev
alexeygrigorev deleted the fix-calendar-slots-date-rot branch November 18, 2026 14:48
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