Lifecycle gate: never had a clean run, and not proven able to fail #9

Open
opened 2026-09-01 21:45:19 +00:00 by paulhitt · 1 comment
paulhitt commented 2026-09-01 21:45:19 +00:00 (Migrated from gitlab.com)

Scripts/lifecycle-gate.sh + UITests/LifecycleGateUITests.swift were added on
2026-09-01 and are committed as a tool, not as evidence.

Outstanding before it can be cited:

  1. It has never completed a run. The first attempt drove the machine to load 591 and
    starved the developer's own emulator and simulator out of existence. It now refuses to
    start above load 20 (FN_GATE_FORCE=1 overrides), but has not been run to completion
    on a quiet machine.
  2. It has not been proven able to go red. A green gate that cannot fail is exactly
    what the iOS CI gate turned out to be. Reverting the sign-in identity fix should turn
    it red on the "Security keys changed" assertion; until that has been observed, a pass
    means nothing.
  3. Each run creates two real accounts on the accounts service. Best-effort deletion at
    the end has not been added.
`Scripts/lifecycle-gate.sh` + `UITests/LifecycleGateUITests.swift` were added on 2026-09-01 and are committed as a tool, **not as evidence**. Outstanding before it can be cited: 1. **It has never completed a run.** The first attempt drove the machine to load 591 and starved the developer's own emulator and simulator out of existence. It now refuses to start above load 20 (`FN_GATE_FORCE=1` overrides), but has not been run to completion on a quiet machine. 2. **It has not been proven able to go red.** A green gate that cannot fail is exactly what the iOS CI gate turned out to be. Reverting the sign-in identity fix should turn it red on the "Security keys changed" assertion; until that has been observed, a pass means nothing. 3. Each run creates two real accounts on the accounts service. Best-effort deletion at the end has not been added.
paulhitt commented 2026-09-01 22:06:29 +00:00 (Migrated from gitlab.com)

mentioned in merge request !44

mentioned in merge request !44
Sign in to join this conversation.