Conversation
| } | ||
| else | ||
| { | ||
| LOG_TEST(log, "Commit request for session {} with type {}, log id {}{}", |
There was a problem hiding this comment.
Just add one message for test.
| } while (false) | ||
|
|
||
|
|
||
| #define LOG_TEST(logger, ...) LOG_IMPL(logger, DB::LogsLevel::test, Poco::Message::PRIO_TEST, __VA_ARGS__) |
There was a problem hiding this comment.
Interesting idea, maybe it should be under #ifdef so that only non-production binaries on CI (i.e. everything with relasetype != relwithdebinfo) will enable those messages?
There was a problem hiding this comment.
We use our production binary in all release tests (and it looks reasonable). I'll think about defence here, maybe at least some runtime check (env variable)...
There was a problem hiding this comment.
I'm suggesting #ifdef here to make then literally no-op in relwithdebinfo/release builds (so that one will not care about additional cost for log messages, i.e. calling of some heavy method), but this has one downside - "variable maybe unused" warnings...
There was a problem hiding this comment.
@azat It costs only one if.
Macro arguments are lazy evaluated.
|
Fuzzer: But now we have MemoryTracker in client, so we can set limit for it, so it should be Ok? |
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Add new log level
<test>for testing environments.