Skip to content

fix: preserve and log backtest retry reasons - #73

Merged
hjcud merged 1 commit into
developfrom
feature/72-retry-observability
Aug 8, 2026
Merged

fix: preserve and log backtest retry reasons#73
hjcud merged 1 commit into
developfrom
feature/72-retry-observability

Conversation

@hjcud

@hjcud hjcud commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Closes #72

What changed

  • preserve the handler/orchestrator retry reason in backtest.run_attempts.failure_code while keeping terminal_reason_code=RETRY_RELEASED
  • configure worker console logging at startup with BACKTEST_LOG_LEVEL (INFO by default)
  • emit retry identifiers and handler exception tracebacks without logging payloads or credentials
  • document the retry-attempt evidence semantics and logging control

No database migration is required; the existing failure_code and terminal_reason_code columns are used.

Verification

  • 1236 passed, 3 skipped, 168 deselected (non-Docker suite)
  • 14 passed (PostgreSQL persistence integration)
  • 10 passed (LocalStack SQS worker integration)
  • ruff check src tests
  • mypy src/backtest_engine tests/conftest.py tests/persistence
  • git diff --check

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.

A retried official backtest run records no reason anywhere (observability only)

1 participant