ci: raise Merkle E2E timeout to 90 min — 60-min cap breached by real runtime (V2-1046) - #178
Merged
Merged
Conversation
…runtime (V2-1046) Third time this cap has been outgrown (20 -> 40 -> 60): on PR #174 the macOS leg passed at 57m09s and the Ubuntu leg was canceled at 60m20s mid-run with no test failure in the log — a pure timeout kill reading as a red X on an unrelated change. 90 min gives the observed ~60-min runtime real headroom while still catching genuine hangs; the neighboring E2E job has no explicit cap, so this stays the tighter bound. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Member
|
Review verdict: APPROVE at This is a narrowly scoped CI-only change: Ubuntu Merkle E2E gets 60 minutes while macOS stays at 45, matching the observed runner asymmetry without weakening the test itself. The workflow expression and self-tests are sound; local verification of The current |
grumbach
added a commit
to grumbach/ant-client
that referenced
this pull request
Aug 25, 2026
Picks up the Merkle E2E timeout raise from WithAutonomi#178 (60 -> 90 min), which is what killed the ubuntu leg of this branch's last CI run at 60m18s with no test failure. Also brings in the beta upgrade channel work from WithAutonomi#173. No conflicts; the branch's own diff against main is byte-for-byte unchanged by this merge.
This was referenced Aug 25, 2026
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linear issue
V2-1046
Risk tier
Compatibility
Semver impact
Test evidence
Evidence the cap is breached by healthy runs, from PR #174's run (an additive API change touching nothing merkle-related): macOS leg passed at 57m09s; Ubuntu leg canceled at 60m20s with no test failure in the log — the workflow's
timeout-minutes: 60killed it mid-run. Third breach of this cap (20 → 40 → 60; history in the workflow comment, now updated). This PR's own Merkle E2E jobs exercise the new bound.New dependency
none
ADR
n/a
Mitigation / rollback
CI-only — revert the single commit; worst case a genuinely hung job holds a runner 30 min longer before the kill.
🤖 Generated with Claude Code