Fix flaky test: `full_client::client::legacy_and_unstable_block_subscription_reconnect`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
I think I've seen this test fail more than once. Can we make it more robust and remove the chance of it failing?
running 1 test
test full_client::client::legacy_and_unstable_block_subscription_reconnect has been running for over 60 seconds
test full_client::client::legacy_and_unstable_block_subscription_reconnect ... FAILED
failures:
failures:
full_client::client::legacy_and_unstable_block_subscription_reconnect
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 85 filtered out; finished in 360.01s
--- STDERR: integration-tests full_client::client::legacy_and_unstable_block_subscription_reconnect ---
thread 'full_client::client::legacy_and_unstable_block_subscription_reconnect' panicked at testing/integration-tests/src/full_client/client/mod.rs:415:1:
Test timedout: Elapsed(())
Contributor guide
No contributing guide indexed for this repository
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
Start with testing/integration-tests/src/full_client/client/mod.rs around line 415 and run full_client::client::legacy_and_unstable_block_subscription_reconnect to reproduce the timeout. Trace the test's reconnect and subscription behavior, then verify it completes reliably without the 60-second timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100