-
Notifications
You must be signed in to change notification settings - Fork 2.6k
broken benchmark for pallet_offences (report_offence_im_online) #10027
Comments
same error with |
slightly different error message on
I was forced to add
|
I believe you need to use the flag |
|
Oh yeah the feature flag is for cargo to compile the substrate binary not a flag for substrate, see example command below
|
The last note clearly shows that your code is outdated. The default execution has been
|
yeah I'm aware. But that's somewhat secondary to this issue. My original goal was just to report this error message I found when benchmarking |
yeah my advice was useless 💀 apologies.
|
maybe the benchmark expect some specific configuration and the way you configured the runtime is inconsistent with this expectation. |
I get the same issue on current master. It needs a fix. Probably a configuration is broken in node-runtime (and is seemingly fine in |
sidenote: out of curiosity where is the result of those benchmark used ? |
I will look into this now.
Babe and Grandpas benchmarks should depend on it, but currently don't. (They need fixing AFAIK) |
Somehow the one test that works, only checks the event emission when run in
If I add this to the failing event tests in report_offence_grandpa , then it also works.Does anyone know, why it is only checking correct event count for test config?
|
I want to run all possible benchmarks on FRAME.
I have
substrate
checked out atmonthly-2021-10
. While running the benchmarks on my machine (i7 CPU, 16Gb RAM), I got stuck with the following error:Is this an actual bug, or did I do something wrong when I started the benchmarking?
The text was updated successfully, but these errors were encountered: