Test the reminder put-off in the zone the page is drawn in #1031
No reviewers
Labels
No labels
accessibility
authentication
breaking change
bug
documentation
enhancement
interface
internationalisation
observability
performance
security
tier
1
tier
2
tier
3
tier/4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Postulo/postulo!1031
Loading…
Reference in a new issue
No description provided.
Delete branch "dated-reminder-zone"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
test_putting_a_reminder_off_moves_it_where_it_standsfailed on the push run of #1017 at 22:45 UTC: the page showed29 Oct 2026, 00:45and the test expected28 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, elseinstance_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