Skip to content

ci: preserve startup diagnostic errors through owned cleanup - #7103

Draft
antuz123 wants to merge 300 commits into
sprintfrom
codex/r5-startup-diagnostic-cleanup
Draft

antuz123 wants to merge 300 commits into
sprintfrom
codex/r5-startup-diagnostic-cleanup

Conversation

@antuz123

@antuz123 antuz123 commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

Diagnostic receipt failures on a319936 could replace the original startup/driver exception and skip owned capture, Metro or device cleanup. This isolated follow-up preserves the primary exception, attempts every cleanup independently, purges only the three new observer raw files, then saves fixed metadata. A failed receipt or unconfirmed cleanup fails a previously successful phase before subsequent probes.

Head: 50a0e3e7c1acbc8417001a6bbd1c691f7b2c08e8; branch codex/r5-startup-diagnostic-cleanup.
Producer #7094 remains unchanged at a319936a754372ff76b10d515dadeded87e88aca.
Patch-only review: a319...50a0. Sprint diff inherits the producer/R5 ancestry; the new package is seven files, 379 additions/67 deletions, one diagnostics feature, approximately 5k added source/test/documentation tokens.

Failed, malformed, empty or truncated inventory queries retain UNKNOWN rather than asserting absence. Valid complete iOS inventories retain presence/absence facts; the Android observer makes positive observations only. #7101's stronger complete Android process/foreground inventory stays canonical when combined; this package retains the unique continuous log/Metro observations. Existing SDK/profile, app source, dependency pins, timeout, assertions and gates are unchanged.

Actual checks on this tree:

  • PASS: 108 Node controls with Node22.23.3; 124 Python controls; actionlint1.7.7 on the three existing native workflows; whitespace.
  • PASS: independent scoped review and 32 affected Python controls. Root independently reran the same 17 startup + 15 driver controls at exact 50a0 and found no blocker; receipt at /workspace/r5-evidence/independent-diag-cleanup-50a0.log.
  • The regression controls call actual smoke/driver finalizers with fake process/device boundaries and force read/save, capture-stop, Metro close/stop, device disposal and purge failures. They are source controls, not emulator/device evidence.
  • Earlier transient fixture recursion was fixed before final passing controls. One lint invocation used a nonexistent workflow filename; the corrected invocation passed. Neither was a production failure.
  • Native iOS/Android and physical checks: NOT RUN on this head. Active original 3eb run 39824790868 attempt 2 remains owned by the coordinator; this package requests no competing execution.

Inherited producer failures stay visible: automatic-backup native matrix, CodeQL and incomplete-matrix/local-validation gates. Producer source contracts passed on synthetic merge a5a5f74; GitHub compare verified zero changed files against a319, without transferring acceptance to 50a0. No cause, native pass or release readiness is claimed here.

Codex local handoff

State: NEEDS_LOCAL
PR: #7103
Base: sprint
Head branch: codex/r5-startup-diagnostic-cleanup
Head commit: 50a0e3e
Goal and acceptance criteria: Preserve original failures through diagnostic cleanup; dispose every owned resource; keep unknown query outcomes truthful.
Changes made: Isolated .github diagnostics safety correction and documentation; producer branches preserved.
Cloud checks: 108 Node / 124 Python/actionlint/whitespace PASS; independent 32 Python PASS; native NOT RUN.
Required local checks: NONE
Local checks requested: NONE for this .github/documentation-only preparation; exact combined R5 hosted/native and physical acceptance remain separate and incomplete. No personal Mac requested.
Risks / known gaps: Infrastructure remains unmerged/untrusted as acceptance; Android/iOS startup causes remain unproven; no native run on this source; full R5 feature/backend/physical matrix still required.
Release readiness: NOT READY. No merge, shared promotion, signing, upload, distribution, deployment or publication.

This branch has not been deployed

No deployments
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.

3 participants