Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests/flaky: ChainHead operation limits test is flaky #7471

Open
lexnv opened this issue Feb 5, 2025 · 0 comments
Open

tests/flaky: ChainHead operation limits test is flaky #7471

lexnv opened this issue Feb 5, 2025 · 0 comments
Labels
I2-bug The node fails to follow expected behavior. T3-RPC_API This PR/Issue is related to RPC APIs.

Comments

@lexnv
Copy link
Contributor

lexnv commented Feb 5, 2025

The ensure_operation_limits_works is flaky:

  • Step1: Subscribe to chainHead_v1_follow with maximum of 1 ongoing operations per subscription
  • Step2: Make a storage query via chainHead_v1_storage
  • Step3: Await OperationStorageDone and by this point, the capacity should be released
  • Step4: Make a runtime API call

MethodResponse::LimitReached => panic!("Expected started response"),

It looks like the capacity reserved by chainHead_v1_storage is not released by the time make a runtime API call:


--- TRY 3 STDERR:        sc-rpc-spec-v2 chain_head::tests::ensure_operation_limits_works ---
thread 'chain_head::tests::ensure_operation_limits_works' panicked at substrate/client/rpc-spec-v2/src/chain_head/tests.rs:2898:41:
Expected started response
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: sc_rpc_spec_v2::chain_head::tests::ensure_operation_limits_works::{{closure}}
   3: tokio::runtime::scheduler::current_thread::Context::enter
   4: tokio::runtime::context::scoped::Scoped<T>::set
   5: tokio::runtime::scheduler::current_thread::CoreGuard::block_on
   6: tokio::runtime::context::runtime::enter_runtime
   7: tokio::runtime::runtime::Runtime::block_on
   8: sc_rpc_spec_v2::chain_head::tests::ensure_operation_limits_works
   9: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Detected by: https://github.com/paritytech/polkadot-sdk/actions/runs/13154495481/job/36708551235

@lexnv lexnv added I2-bug The node fails to follow expected behavior. T3-RPC_API This PR/Issue is related to RPC APIs. labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I2-bug The node fails to follow expected behavior. T3-RPC_API This PR/Issue is related to RPC APIs.
Projects
None yet
Development

No branches or pull requests

1 participant