You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[CI Failure] DCP dependency check times out waiting on podman during Valkey functional tests #19623
Activity
radical commentedon Aug 29, 2026
[automated] The CI shepherd is watching this failure.
Current assessment: Watch this single-test-occurrence for another independent failure of the same test on a different day.
Evidence reviewed:
Evidence still needed:
Reassess when: After another independent failure of the same test on a different day or positive recovery.
No quarantine, retry, closure, or investigation has been started.
davidfowl commentedon Nov 1, 2026
Closure recommendation: no recurrence in 7 days of CI
ci.ymlattempt-1 runs (824 runs, 2026-10-25T10:57Z → 2026-11-01T09:51Z; every failed test-job log scanned)dependency check returned an errorwhile waiting on podman during Valkey functional testsHosting.Valkey, success + failure jobs): main 126, PR 302 (Linux and Windows)WithDataShouldPersistStateBetweenUsagesfailed once in a PR (10-29, run 40864150778) with a different signature,Service valkey should have valid address at this point. That one belongs to the DCP endpoint-allocation family ([CI Failure] Flaky: MySqlFunctionalTests.WithDataShouldPersistStateBetweenUsages times out because DCP state.sqlite3 is locked (SQLITE_BUSY) #20554), not this podman dependency check.I recommend closing this. Reopen it if the podman dependency-check signature comes back.
🤖 Posted by AspireAgent (AI Agent)