Skip to content

[CI] Diagnose and fix offline paired fixture deadline failures without weakening coverage #61

Description

@jjangg96

Goal

Make exhaustive offline paired-fixture CI reliably complete within the existing per-process deadline without omitting tests or weakening live-helper exclusions.

Evidence and scope

PR #59 head 3cb19ce changes only documentation. Hosted run 34193163898/job101955210094 fails the G01 livecanary collection/listener process at its 120s package deadline, with TestObserveCancellationAndApprovalExpiry/approval-expiry listed as running for 0s. This does not prove the individual test hung; diagnose cumulative workload versus blocking before fixing. Earlier collection checks approach 100-107s. Do not blindly rerun CI or widen deadlines.

Independent user-authorized parallel task, Luna/max, after #54. Own scripts/check-offline-experiments.sh, scripts/tooling_test.go and docs/CI.md; coordinate any additional file with issue #60 integrator. No overlap with runtime/CLI changes or PR59 readiness document.

Acceptance

  • Reproduce/measure actual scoped workload or blocking cause with pinned Go1.26.8 and race, and record evidence honestly.
  • Preserve every test, existing helper/live tags, sequential failure propagation, fixed toolchain and timeout bounds.
  • If cumulative workload is confirmed, use explicit exhaustive disjoint static groups rather than dropped tests or dynamic retries. Real generated passing/failing sentinels must prove every group executes once and failures propagate.
  • Meaningful failing tooling regression before minimal implementation; relevant green/boundary and full checks after.
  • No live runners, Docker/Lima/context, App/Keychain/launchd, secrets or private logs.
  • One focused PR with red evidence, exactcommands/results/remaininggaps/rollback; independent review, exact-head clean Codex and CI before SHA-matched merge.

Do not close parent #1/#2 or claim live acceptance. Reuse coordinator parent Goal; no new native Goal.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    release:mvpApproved delivery sequencing; does not change acceptance or dependency gates

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions