Skip to content

fix: use configurable block wait timeout in TestSyncToTipMocha#7018

Draft
rootulp wants to merge 1 commit intomainfrom
rootulp/fix-sync-to-tip-timeout
Draft

fix: use configurable block wait timeout in TestSyncToTipMocha#7018
rootulp wants to merge 1 commit intomainfrom
rootulp/fix-sync-to-tip-timeout

Conversation

@rootulp
Copy link
Copy Markdown
Collaborator

@rootulp rootulp commented Apr 9, 2026

Summary

  • Bump tastora to include WithBlockWaitTimeout (tastora#189)
  • Use WithBlockWaitTimeout(syncToTipTimeout) in TestSyncToTipMocha so the 10-minute test timeout also applies to the block wait in Chain.Start()
  • Previously, Chain.Start() had a hardcoded 120s block wait which was too short for state sync nodes connecting to Mocha

Closes #7017

Test plan

  • Verify TestSyncToTipMocha passes in nightly CI after tastora#189 is merged and a release is tagged
  • Verify other docker-e2e tests are unaffected (they use the default 120s timeout)

🤖 Generated with Claude Code

The sync-to-tip test was failing because tastora's Chain.Start() has a
hardcoded 120-second timeout waiting for 2 blocks. State syncing to
Mocha consumes most of that time, leaving insufficient time for block
sync. Use the new WithBlockWaitTimeout to set the timeout to the
test's syncToTipTimeout (10 minutes).

Closes #7017

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@rootulp rootulp self-assigned this Apr 9, 2026
@rootulp
Copy link
Copy Markdown
Collaborator Author

rootulp commented Apr 9, 2026

Draft mode until celestiaorg/tastora#189 merges and gets released

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: TestSyncToTipMocha fails due to hardcoded 120s block wait timeout in tastora

2 participants