-
Notifications
You must be signed in to change notification settings - Fork 8
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
staking-miner integration tests failed against latest polkadot build. #472
Comments
I did some investigation and it turns out that paritytech/polkadot#6762 broke things for us. For some reason the trimming stuff from the I have some assumptions in the code where for instance main branch
dev branch with some hacks➜ staking-miner git:(na-debug-weights) ✗ ./target/debug/staking-miner --uri ws://localhost:9944 monitor --seed-or-path //Alice --dry-run --listen finalized seq-phragmen
2023-03-06T15:38:49.042019Z DEBUG staking-miner: attempting to connect to "ws://localhost:9944"
2023-03-06T15:38:49.134230Z INFO staking-miner: Started prometheus endpoint on http://0.0.0.0:9999
2023-03-06T15:38:49.134256Z INFO staking-miner: Connected to chain: polkadot
2023-03-06T15:38:49.134310Z TRACE staking-miner: updating metadata constant `ElectionProviderMultiPhase::SignedMaxWeight`: 1471776990000
2023-03-06T15:38:49.134319Z TRACE staking-miner: updating metadata constant `ElectionProviderMultiPhase::MinerMaxLength`: 3538944
2023-03-06T15:38:49.134326Z TRACE staking-miner: updating metadata constant `ElectionProviderMultiPhase::MinerMaxVotesPerVoter`: 16
2023-03-06T15:38:49.209317Z INFO staking-miner: Loaded account Id(AccountId32([212, 53, 147, 199, 21, 253, 211, 28, 97, 20, 26, 189, 4, 169, 159, 214, 130, 44, 133, 88, 133, 76, 205, 227, 154, 86, 132, 231, 165, 109, 162, 125])), AccountInfo { nonce: 3, consumers: 0, providers: 1, sufficients: 0, data: AccountData { free: 9998799308172092, reserved: 0, misc_frozen: 0, fee_frozen: 0 } }
2023-03-06T15:38:49.210735Z TRACE staking-miner: new event at #236 (0xddc670205cd4e48585453671de791524e6127431d1f036d683ee073de2c6c2e4)
2023-03-06T15:38:49.212290Z DEBUG staking-miner: ensure_signed_phase failed: IncorrectPhase; skipping block: 236
2023-03-06T15:38:49.245253Z WARN staking-miner: upgrade to version: 9370 failed: SameVersion
2023-03-06T15:38:50.295207Z TRACE staking-miner: new event at #237 (0x0db1ff1531845223ff40ed685fff099cbfa6384692dcf643e1b275c28a9e62f0)
2023-03-06T15:38:50.296987Z DEBUG staking-miner: ensure_signed_phase failed: IncorrectPhase; skipping block: 237
2023-03-06T15:38:58.303340Z TRACE staking-miner: new event at #238 (0x158cfd3bd586ea06b234c25a40577478cef700dae487d1e9f0638d663f6963e0)
2023-03-06T15:38:58.305901Z DEBUG staking-miner: ensure_signed_phase failed: IncorrectPhase; skipping block: 238
2023-03-06T15:39:02.307159Z TRACE staking-miner: new event at #239 (0x62d737cb06f3c51a8cb67dc51bd32d5c14748e9569ad4701cf4ba117b694b09c)
2023-03-06T15:39:02.309611Z DEBUG staking-miner: ensure_signed_phase failed: IncorrectPhase; skipping block: 239
2023-03-06T15:39:10.315295Z TRACE staking-miner: new event at #240 (0x47dbe004cec7310f555a7c10ce129b5de7ca0655f04e952dfb97874d4352076f)
2023-03-06T15:39:10.318146Z DEBUG staking-miner: ensure_signed_phase failed: IncorrectPhase; skipping block: 240
2023-03-06T15:39:14.320716Z TRACE staking-miner: new event at #241 (0x7b539a845d899d9c6ca8bb5e5234cc31e27b8332ac1f6a17b3d5a9565000877b)
2023-03-06T15:39:14.328131Z INFO staking-miner: voters=[(AccountId32([190, 93, 219, 21, 121, 183, 46, 132, 82, 79, 194, 158, 120, 96, 158, 60, 175, 66, 232, 90, 161, 24, 235, 254, 11, 10, 212, 4, 181, 189, 210, 95]), 1000000000000, BoundedVec([AccountId32([190, 93, 219, 21, 121, 183, 46, 132, 82, 79, 194, 158, 120, 96, 158, 60, 175, 66, 232, 90, 161, 24, 235, 254, 11, 10, 212, 4, 181, 189, 210, 95])], 16))], desired_targets=1
2023-03-06T15:39:14.328659Z TRACE staking-miner: voters=1, targets=1, active_voters=1, desired_targets=1
2023-03-06T15:39:14.328697Z TRACE staking-miner: Solution with voters=1, desired_targets=1
2023-03-06T15:39:14.330681Z TRACE staking-miner: Received weight of `Solution Extrinsic` from remote node: Weight { ref_time: 5037560276, proof_size: 9317 }
2023-03-06T15:39:14.330719Z TRACE staking-miner: voters=1, targets=1, active_voters=1, desired_targets=1
2023-03-06T15:39:14.330735Z TRACE staking-miner: Solution with voters=1, desired_targets=1
2023-03-06T15:39:14.331734Z TRACE staking-miner: Received weight of `Solution Extrinsic` from remote node: Weight { ref_time: 5037560276, proof_size: 9317 }
2023-03-06T15:39:14.331752Z TRACE staking-miner: voters=1, targets=1, active_voters=0, desired_targets=1
thread 'tokio-runtime-worker' panicked at 'weight_with(0) <= Weight(ref_time: 1471776990000, proof_size: 0)', /home/niklasad1/.cargo/git/checkouts/substrate-7e08433d4c370a21/c408123/frame/election-provider-multi-phase/src/unsigned.rs:684:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2023-03-06T15:39:14.331941Z INFO staking-miner: round of execution finished. outcome = Err(Other("JoinError::Panic(Id(42), ...)"))
Error: Other("JoinError::Panic(Id(42), ...)")
dev branch --release with some hacks
The question is really whether this a bug in polkadot or "wrong assumptions in the repo", I could probably "workaround" this such as provide max weight/min weight but I'm confused and not really follow why the trimming stuff occurs by the weight stuff in that PR. //cc @kianenigma @gpestana |
Go to https://gitlab.parity.io/parity/mirrors/staking-miner-v2/-/pipelines/251999 to see details about the failure.
The text was updated successfully, but these errors were encountered: