Skip to content

fix: use 24-hour days for AM startup log rotation - #107

Open
robjarawan wants to merge 1 commit into
developmentfrom
fix/am-startup-log-rotation
Open

fix: use 24-hour days for AM startup log rotation#107
robjarawan wants to merge 1 commit into
developmentfrom
fix/am-startup-log-rotation

Conversation

@robjarawan

@robjarawan robjarawan commented Jul 14, 2026

Copy link
Copy Markdown
Owner
Summary
  • use 86,400 seconds for the day threshold and divisor in the AM child startup logging helper
  • align cfglogs() with the already-correct normal instance logging path
  • verify exact handler arguments for 12h, 1d, and 2d using deterministic constructor mocks

Scope is intentionally limited: this corrects the short-lived AM child startup handler. It does not claim that running workers previously retained a two-day rotation cadence.

Tests
  • cfglogs interval regression — 3 passed
  • pytest -q tests/sarracenia/config_test.py — 19 passed
  • available repository suite — 299 passed, 2 skipped
  • compile, diff, and 119-character checks passed

Closes #36.

@robjarawan robjarawan added the bug Something isn't working label Jul 14, 2026
@robjarawan robjarawan self-assigned this Jul 14, 2026
@github-actions

Copy link
Copy Markdown

Test Results

377 tests   375 ✅  1m 30s ⏱️
  1 suites    1 💤
  1 files      1 ❌

For more details on these failures, see this check.

Results for commit a597c23.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AM child startup logging uses a 34,560-second day in cfglogs

1 participant