ethereum-optimism / ethereum-optimism/optimism

[acceptance] Use block times for waits/timeouts instead of hardcoding values

Open
#16,598 0 comments 0 reactions 0 assignees View on GitHub
A-acceptance-tests M-needs-triage
Dominant language
Go
Stars
6.5k
Forks
4k
Avg merge
2d 15h
Merged PRs (30d)
145

Description

**Is your feature request related to a problem? Please describe.**
Currently we're hardcoding long timeouts for tests to succeed on persistent devnets.

**Describe the solution you'd like**
Use the block time to potentially calculate the timeouts.

**Describe alternatives you've considered**

**Additional context**

Contributor guide

Open the contributing guide

Research direction

Start by locating the acceptance tests that hardcode long waits and timeouts for persistent devnets, then identify how the devnet block time is exposed. Define the timeout calculations around that block time and verify that the acceptance suite still succeeds on persistent devnets. Done means the relevant waits no longer rely on fixed long values.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.