Disable logging in runtime when enabling runtime-benchmarks
#2901
Conversation
athei
added
A0-please_review
| @@ -102,6 +102,7 @@ std = [ | |||
| "xcm/std", | |||
| ] | |||
| runtime-benchmarks = [ | |||
| "sp-api/disable-logging", | |||
There was a problem hiding this comment.
Don't we need to enable this in other places as well?
There was a problem hiding this comment.
The common runtime is a dependency of all other runtimes. AFAIK this is the only place where we need to at it. It does not seem to be applicable to bridge and xcm runtimes because those don't depend on sp-api. Maybe someone else can step in with more knowledge about those runtimes.
There was a problem hiding this comment.
Sounds like we could have some kind of test to make sure we don't make this mistake again.
There was a problem hiding this comment.
You mean having logging enabled during benchmarking by accident?
There was a problem hiding this comment.
yes, but it is probably a PITA
There was a problem hiding this comment.
I have no idea on how to construct such a test other than some benchmark which looks for regressions. And something like that would be really nice to have anyways. After each benchmarks of the contracts pallet I need to manually look through a ton of benchmarks and scan for regressions. Would be nice to have this automated.
|
Do we need to re-run any benchmarks? |
|
Every benchmark which was ran since paritytech/substrate#8128 was merged is potentially flawed when it emits a substantial amount of log messages. That said, for |
|
@bkchr can we do this by simply adding |
|
Yeah, this is what I wanted to express with my message xD |
|
Ok I got it. Would be more appropriate to discuss this in the substrate version of this PR, though. I will update that one with your suggestion. |
|
I tested it and it doesn't work... Cargo feature resolution is just the best piece of software I know... :( |
I can confirm that. So we just keep this PR the way it is. |
|
Superseded by paritytech/substrate#8655 |
Same PR as paritytech/substrate#8638
This is different from the substrate PR in that here the logs are automatically disabled whenever the
runtime-benchmarksfeature is supplied. On substrate this is not possible because of tests which parse log output.