fix: stabilize two CI test failures (Paris today, worker cancel race) #307
Closed
nessar
wants to merge 3 commits from
feature/ci-test-stability into develop
pull from: feature/ci-test-stability
merge into: nessar:develop
nessar:develop
nessar:feature/obligation-solution-ranking
nessar:feature/bun-migration
nessar:feature/planning-architecture
nessar:feature/incremental-exact-scoring
nessar:feature/benchmark-performance
nessar:feature/verify-trace-free-planning
nessar:feature/remove-decision-trace
nessar:feature/gitea-actions
nessar:feature/gitflow-ci
nessar:main
nessar:select-duration
nessar:dependabot/npm_and_yarn/typescript-6.0.3
nessar:dependabot/github_actions/docker/build-push-action-7
nessar:dependabot/github_actions/docker/login-action-4
nessar:dependabot/github_actions/docker/metadata-action-6
nessar:dependabot/github_actions/docker/setup-buildx-action-4
nessar:dependabot/github_actions/actions/upload-artifact-7
nessar:copilot/sub-pr-61-another-one
nessar:copilot/sub-pr-61-again
nessar:copilot/sub-pr-61
nessar:copilot/sub-pr-49
nessar:copilot/sub-pr-37
nessar:copilot/update-ci-cd-pipeline
nessar:copilot/refactor-duplicated-code
3
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
036b13613c |
test(calendar): pin the clock for the Paris today marker
CI / policy (push) Successful in 26s
CI / validate (push) Successful in 28s
CI / build (push) Successful in 23s
CI / benchmark (push) Successful in 1m26s
CI / security (push) Successful in 1m14s
CI / test (push) Successful in 1m58s
CI / images (push) Successful in 57s
CI / required (push) Successful in 3s
CI / policy (pull_request) Failing after 10s
CI / validate (pull_request) Successful in 26s
CI / build (pull_request) Successful in 21s
CI / benchmark (pull_request) Successful in 1m0s
CI / security (pull_request) Successful in 58s
CI / test (pull_request) Successful in 1m52s
CI / images (pull_request) Skipped
CI / required (pull_request) Failing after 1s
The test of the today marker read the wall clock, so it only exercised the Paris/local date mismatch between 22:00 and 24:00 UTC and passed with or without the fix the rest of the day. Pin the clock to 22:16 UTC, already the next day in Paris, so a UTC runner fails without the fix at any time. Refs #301 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
af20c96f01 |
test(planning): hold the worker until the preparation cancel arrives
CI / policy (push) Successful in 16s
CI / validate (push) Successful in 29s
CI / build (push) Successful in 20s
CI / benchmark (push) Successful in 1m27s
CI / security (push) Successful in 1m0s
CI / test (push) Successful in 1m57s
CI / images (push) Successful in 1m20s
CI / required (push) Successful in 1s
CI / policy (pull_request) Successful in 8s
CI / validate (pull_request) Successful in 23s
CI / test (pull_request) Successful in 1m51s
CI / build (pull_request) Successful in 38s
CI / security (pull_request) Successful in 1m1s
CI / benchmark (pull_request) Successful in 46s
CI / images (pull_request) Successful in 51s
CI / required (pull_request) Successful in 2s
The worker reads its queue only between event-loop turns, so the calendar preparation could finish before the cancel sent on its second progress update arrived, and the test received a complete plan. Use the real-worker harness hold already applied to the checkpoint cancellation test, and cancel on the first preparation update so the hold is released. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
f458a83599 |
fix(calendar): mark today on the Europe/Paris date
The calendar highlighted today from the browser's local date while the default planning horizon starts on the Europe/Paris date, so the two disagreed for a few hours a day (and always, for users in another time zone). The horizon's first day was then not marked as today. This also failed the CI test run in UTC containers between 22:00 and 24:00 UTC. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |