OpenZeppelin / OpenZeppelin/Event-Scanner
Investigate potential flaky test test_to_block_above_latest_returns_error and test_subscription_lagged_error
Open
Nobody has claimed this yet.
priority: critical
type: bug
type: test
- Dominant language
- Rust
- Stars
- 19
- Forks
- 7
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 4
Description
For some reason these two tests have failed locally. If this happens in CI we need to investigate why / fix this - for now I cant reliably get them to fail.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate test_to_block_above_latest_returns_error and test_subscription_lagged_error in the Rust test suite and run them repeatedly to reproduce the failures. Investigate the cause if they fail in local or CI runs; done means the flaky behavior is understood and the tests reliably pass, or the issue has a documented fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100