flaky test: TestActivatorWakeFailuresReleaseLeaseOnce/restore double lease release under full-suite load Issue open
Migrated from github.com/carlosframework/platform issue #155, opened 2026-08-12. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: Intermittent double lease release in the activator's restore path, or racy counting in the test, still uninvestigated.
---
Seen 2026-08-12 during an unrelated branch's gate (ha-snapshot, which does not touch internal/activator):
--- FAIL: TestActivatorWakeFailuresReleaseLeaseOnce (0.02s)
--- FAIL: TestActivatorWakeFailuresReleaseLeaseOnce/restore (0.01s)
activator_test.go:799: lease releases = 2 after a failed restore, want exactly 1Reproduction: intermittent — appeared once in three go test ./... -count=1 full-suite runs; 30 focused -run iterations pass on both the branch and pristine origin/main (a73539f), so it needs full-suite parallel load/timing to trigger. Pre-existing on main; either the restore path can genuinely double-release a lease under contention (production-relevant) or the test's counting is racy. Worth a look before it starts failing CI runs at random.
🤖 Generated with Claude Code