Fix history_depth testing (#662)

* testing/staking: `history_depth` storage is now a constant

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* artifacts: Update metadata from `9ffe6e9e3da`

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* testing: Update `polkadot.rs` from `9ffe6e9e3da`

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* examples: Update comment wrt polkadot version

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* codegen: Fix clippy

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
This commit is contained in:
Alexandru Vasile
2022-09-22 18:02:30 +03:00
committed by GitHub
parent e233dd6bcb
commit f48a5df2ca
20 changed files with 3888 additions and 1315 deletions
File diff suppressed because it is too large Load Diff
@@ -219,11 +219,8 @@ async fn tx_bond() -> Result<(), Error> {
async fn storage_history_depth() -> Result<(), Error> {
let ctx = test_context().await;
let api = ctx.client();
let history_depth_addr = node_runtime::storage().staking().history_depth();
let history_depth = api
.storage()
.fetch_or_default(&history_depth_addr, None)
.await?;
let history_depth_addr = node_runtime::constants().staking().history_depth();
let history_depth = api.constants().at(&history_depth_addr)?;
assert_eq!(history_depth, 84);
Ok(())
}