Skip to content

test: fast-fail CIT on fatal crash loop and diagnose localhost binds - #38

Merged
ahze merged 1 commit into
mainfrom
cit/fast-fail-diagnostics
Oct 5, 2026
Merged

ahze merged 1 commit into
mainfrom
cit/fast-fail-diagnostics

Conversation

@ahze

@ahze ahze commented Oct 5, 2026

Copy link
Copy Markdown
Member
  • Fast-fail container ready polling immediately on fatal crash signatures (panic:, Fatal error:, Segmentation fault, core dumped) or a crash loop (3+ s6 service crashes), avoiding long timeouts on dead containers.
  • Safely allow transient single service crashes with s6 recovery, non-fatal .NET background exceptions, and IPv6 dual-stack bind messages.
  • Dump 50 lines of logs instead of 20 when container crashes or exits.
  • Run sockstat inside container when port check fails to detect 127.0.0.1 vs 0.0.0.0 binding issues.
  • Capture HTTP 5xx response bodies in CIT health checks.
  • Accelerate test suite by parameterizing poll_interval in socket/health timeouts (5.3s vs 10.6s).
  • Fix ruff lint warnings in docs.py and lint.py.

- Fast-fail container ready polling immediately on fatal crash signatures
  (panic:, Fatal error:, Segmentation fault, core dumped) or a crash loop
  (3+ s6 service crashes), avoiding long timeouts on dead containers.
- Safely allow transient single service crashes with s6 recovery,
  non-fatal .NET background exceptions, and IPv6 dual-stack bind messages.
- Dump 50 lines of logs instead of 20 when container crashes or exits.
- Run sockstat inside container when port check fails to detect 127.0.0.1
  vs 0.0.0.0 binding issues.
- Capture HTTP 5xx response bodies in CIT health checks.
- Accelerate test suite by parameterizing poll_interval in socket/health
  timeouts (5.3s vs 10.6s).
- Fix ruff lint warnings in docs.py and lint.py.
@ahze
ahze merged commit 6721dff into main Oct 5, 2026
2 checks passed
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.

1 participant