feat(gtest): make log more customizable#3072
Merged
Merged
Conversation
ukint-vs
approved these changes
Aug 16, 2023
gshep
approved these changes
Aug 16, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As for now,
gtestis quite noisy with default logging settings. Let's distinguish"gtest"target from"gwasm".@gear-tech/dev
Release Notes
gtestlogging less noisy and more configurablegtestlib had some actions logged to stdout that were not required for every Wasm execution. Now it is possible to enable these logs using a newSystem::init_verbose_loggerfunction or just enabling"gtest"log target to thedebuglevel in theRUST_LOGenvironment variable.