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
Came across some issues with how we are running benchmarks with @enddynayn
The frequency-bench chain is enabled for the frequency feature, but should only be enabled for runtime-benchmarks feature
When we are running the benchmarks in run_benchmarks.sh it is running with features=runtime-benchmarks,frequency-lint-check. Should it instead be running with features=runtime-benchmarks,frequency?
Would this cause issues with non-mainnet pallets?
Perhaps it should run this way for release only?
node/service/src/chain_spec/frequency.rsbenchmark_mainnet_config should be limited to the runtime-benchmarks feature
The text was updated successfully, but these errors were encountered:
Aside form pallets inclusion or exclusion, using frequency feature or not would have effect if we have feature based logic in our pallets that might alter the weight of benchmarks. I don't think we have anything like that
Came across some issues with how we are running benchmarks with @enddynayn
frequency-bench
chain is enabled for thefrequency
feature, but should only be enabled forruntime-benchmarks
featurerun_benchmarks.sh
it is running withfeatures=runtime-benchmarks,frequency-lint-check
. Should it instead be running withfeatures=runtime-benchmarks,frequency
?node/service/src/chain_spec/frequency.rs
benchmark_mainnet_config
should be limited to theruntime-benchmarks
featureThe text was updated successfully, but these errors were encountered: