recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
f7971d949da35af85e86144d753119a3d5f2daf2
cc-ci-orchestrator/cc-ci-plan/REBOOTS.md
autonomic-bot 36a6c9872a orchestrator: reboot-resilience + session auto-resume + full session plan/tooling 
Reboot survival for the Pi orchestrator host:
- systemd unit cc-ci-plan/systemd/cc-ci-loops.service (installed + enabled): on boot
  records the reboot, starts loops+watchdog (RESUME_PHASE=1), and resumes the
  orchestrator session.
- reboot-log.sh: boot_id-gated reboot record -> REBOOTS.md (manual restarts don't count).
- launch-orchestrator.sh: injects an AGENTS.md startup nudge so an auto-resumed
  orchestrator announces itself (PushNotification) + reports reboots.
- AGENTS.md: on-startup notify routine documented.

Plans/tooling accumulated this session:
- plan-phase1d (generic suite), 1e (harness corrections), phase4 (final review),
  sso-dep-testing, orchestrator-migration (parked), test-e2e-testme-acceptance.
- launch.sh: 1d/1e/2/2b/3/4 phase sequence, machine-docs-aware state resolution,
  limit-stall re-nudge, INBOX side-channel detection.
- plan.md §6.1/§7: artifact-layer isolation, INBOX, 5-min long-run polling, DEFERRED.
- prompts: isolation discipline + INBOX + pacing.
- .gitignore: harden (.sops/, cc-ci-secrets/, .claude/, *.tmp.*).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-28 20:28:10 +01:00

929 B
Raw Blame History

Reboot log — cc-ci orchestrator Pi

One line per genuine reboot of the orchestrator Pi (raspberrypi), appended automatically by reboot-log.sh (ExecStartPre of cc-ci-loops.service, boot_id-gated so manual service restarts are NOT counted). The Pi hosts the Builder + Adversary loops + watchdog; a reboot drops the tmux sessions (and this orchestrator session), and cc-ci-loops.service restarts the loops on boot. Count the lines below to see how often it's happening.

Reboots

  • 2026-05-28 (~19:?? BST) — reboot (backfilled from memory; mid-Phase-2). Orchestrator + loops were down until manually relaunched. This pre-dates the systemd auto-restart service.
  • 2026-05-28 (~20:02 BST) — reboot (backfilled from memory; uptime showed 5 min at 20:07). Loops manually relaunched at phase 2; this is what prompted adding cc-ci-loops.service + auto-logging. Auto-logging is live from the next reboot onward.