You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am just thinking, as a part of fellows repo issue, I would like to add CI pipeline for testing "benchmarks" - like we have short-benchmark* jobs in polkadot-sdk.
Encointer was merged to fellows without even noticing that benchmarks do not work see.
We've merged chain-spec-generator to fellows, so the only puzzle missing is how to run them without need to rebuild polkadot binary in fellows CI. E.g.
I think, there are two solutions:
release polkadot binary built with `--features runtime-benchmarks"
extend this try-runtime-cli - we are already using this binary for check-migrations, so maybe it could be possible to extend and just reuse this binary for running short benchmarks.
I think that testing/running benchmarks seems to be part of "try runtime" functionality :)
The text was updated successfully, but these errors were encountered:
so the only puzzle missing is how to run them without need to rebuild polkadot binary in fellows CI. E.g.
Yea i thought about this. It should be possible to build the benchmark pallet command as freestanding binary that works with any runtime.
But i dont see this as part of try-runtime. It can just be a freestanding bench runner binary.
For the other benchmarking commands its more difficult, since they actually use the node to author a block.
I am just thinking, as a part of fellows repo issue, I would like to add CI pipeline for testing "benchmarks" - like we have
short-benchmark*
jobs inpolkadot-sdk
.Encointer was merged to fellows without even noticing that benchmarks do not work see.
We've merged
chain-spec-generator
to fellows, so the only puzzle missing is how to run them without need to rebuildpolkadot
binary in fellows CI. E.g.I think, there are two solutions:
polkadot
binary built with `--features runtime-benchmarks"try-runtime-cli
- we are already using this binary forcheck-migrations
, so maybe it could be possible to extend and just reuse this binary for running short benchmarks.I think that testing/running benchmarks seems to be part of "try runtime" functionality :)
The text was updated successfully, but these errors were encountered: