Skip to content

eth/executionclient: widen the flaky tests' context budgets (#2970, convergence) - #2977

Open
momosh-ssv wants to merge 2 commits into
integration/boole-convergencefrom
fix/2970-deflake-convergence
Open

eth/executionclient: widen the flaky tests' context budgets (#2970, convergence)#2977
momosh-ssv wants to merge 2 commits into
integration/boole-convergencefrom
fix/2970-deflake-convergence

Conversation

@momosh-ssv

Copy link
Copy Markdown
Contributor

Cherry-pick of #2976 onto integration/boole-convergence — today TestStreamLogs/TestSimSSV failed on essentially every CI run of the convergence-based PRs (#2971 needed four attempts), and a fix on stage doesn't reach their CI. Same two one-line test-only budget bumps (5s → 30s); the two branches' copies of the file are identical, so the eventual #2941 merge dedups cleanly. See #2976 for the root-cause analysis.

TestStreamLogs/successfully_streams_logs and TestSimSSV shared a single
5s context serving both as the production streaming context and the
tests' own poll deadline - on loaded CI runners scheduling jitter alone
blew the budget while everything was progressing (streamedLogsCount: 25
of 30 at expiry). Both wait loops already react to their condition
immediately, so only the CI-safety margin changes (5s -> 30s at the two
call sites); the fast path is unaffected and other tests keep their
budgets.

Refs #2970 (these two were failing essentially every CI run today,
blocking unrelated PRs).
@momosh-ssv
momosh-ssv requested review from a team as code owners July 30, 2026 14:00
@greptile-apps

greptile-apps Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Widens the context deadlines in two flaky execution-client integration tests from 5 seconds to 30 seconds while preserving fast-path polling and event-driven completion.

  • Increases the TestStreamLogs CI scheduling-jitter budget.
  • Increases the TestSimSSV budget for seven events and follow-distance block commits.

Confidence Score: 5/5

The PR appears safe to merge because it only widens test deadlines without changing production behavior or successful test completion paths.

Both affected tests still complete as soon as their polling or event conditions succeed, while the longer contexts reduce failures caused by scheduling delays.

Important Files Changed

Filename Overview
eth/executionclient/execution_client_test.go The two test-only timeout increases leave successful execution unchanged and provide additional time for asynchronous simulator event processing on loaded CI runners.

Reviews (1): Last reviewed commit: "eth/executionclient: widen the flaky tes..." | Re-trigger Greptile

The first pass widened only the two named flaky tests, but the same
loaded-runner conditions promptly failed TestFetchHistoricalLogs on its
own 5s budget (died at 8.3s). Every setupTestEnv budget in the package
is condition-driven waiting under the hood, so widen them all to 30s -
the fast path is unaffected.
@codecov

codecov Bot commented Jul 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.1%. Comparing base (09a74d7) to head (8cb53a9).

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

1 participant