Test the reminder put-off in the zone the page is drawn in #1031

Merged
tiagoagueda merged 1 commit from dated-reminder-zone into main 2026-10-22 00:57:05 +00:00
Owner

test_putting_a_reminder_off_moves_it_where_it_stands failed on the push run of #1017 at 22:45 UTC: the page showed 29 Oct 2026, 00:45 and the test expected 28 Oct 2026.

Cause

The test took "next week" with timezone.localtime(...), in the test process's zone. The page draws the date in the person's zone, else the instance's (Europe/Paris). Between 22:00 and midnight UTC the two zones are on different days, so the test failed for those two hours of every day, on any branch. That is why #1017's browser job passed on one run and failed on the next.

What changed

The expected day is computed in the zone the page uses: applicant.profile.time_zone, else instance_zone().

Tests

The test passes locally. It fails only in the two evening hours, so the real check is a CI run at that time of day.

Library check

None needed.

🤖 Generated with Claude Code

`test_putting_a_reminder_off_moves_it_where_it_stands` failed on the push run of #1017 at 22:45 UTC: the page showed `29 Oct 2026, 00:45` and the test expected `28 Oct 2026`. ## Cause The test took "next week" with `timezone.localtime(...)`, in the test process's zone. The page draws the date in the person's zone, else the instance's (`Europe/Paris`). Between 22:00 and midnight UTC the two zones are on different days, so the test failed for those two hours of every day, on any branch. That is why #1017's browser job passed on one run and failed on the next. ## What changed The expected day is computed in the zone the page uses: `applicant.profile.time_zone`, else `instance_zone()`. ## Tests The test passes locally. It fails only in the two evening hours, so the real check is a CI run at that time of day. ## Library check None needed. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Test the reminder put-off in the zone the page is drawn in
Some checks failed
CI / Unit tests and coverage (Python 3.14) (pull_request) Failing after 12m57s
CI / Checks: lint, migrations, catalogues, settings, built files (pull_request) Successful in 2m25s
CI / Database tests on PostgreSQL (pull_request) Successful in 3m53s
CI / Security audit (pull_request) Has been cancelled
CI / Browser tests (Chromium) (pull_request) Has been cancelled
bcd977034e
The test took 'next week' in the test process's zone and the page draws it in the person's,
or the instance's (Europe/Paris). Between 22:00 and midnight UTC those are different days,
and the test failed for those two hours every day: the push run of #1017 at 22:45 UTC.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
tiagoagueda deleted branch dated-reminder-zone 2026-10-22 00:57:05 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Postulo/postulo!1031
No description provided.