ethereum-optimism / ethereum-optimism/optimism
op-acceptance-tests: resolve TestMaxSafeLagStallAndResume kona-node skip
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
## Summary
[`TestMaxSafeLagStallAndResume`](https://github.com/ethereum-optimism/optimism/blob/develop/op-acceptance-tests/tests/sequencer/max_safe_lag_test.go) is skipped when the acceptance suite runs against kona-node.
The test exercises `sequencer.max-safe-lag`, which is currently an op-node-specific sequencer feature rather than shared CL behavior.
## Required work
Decide whether Kona should implement equivalent max-safe-lag behavior. If so, add it and enable the test; otherwise make the client-specific scope explicit so the intentional exclusion is not tracked as an unexplained compatibility skip.
## Acceptance criteria
- [ ] The root cause and resolution are documented.
- [ ] The Kona exclusion is either removed or represented as an explicit, documented client-feature scope.
- [ ] The resolution is documented and the test is either enabled for Kona or explicitly scoped to the client feature it covers.
- [ ] Existing op-node coverage continues to pass.
## Related
- https://github.com/ethereum-optimism/optimism/issues/17936
- Parent inventory: https://github.com/ethereum-optimism/protocol-team/issues/101
Contributor guide
Assessment
This issue has not been assessed yet.