-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce console noise coming from unit tests: #4166
Conversation
A few unit tests have historically generated a lot of noise to the console from log writes. This noise was not useful and made it harder to locate actual test failures. By changing the log level of these tests from - severities::kError to - severities::kDisabled it was possible to remove that noise coming from the logs.
I noticed about 135 lines fewer with your change, but I still picked up on some noise from
Maybe it's not an issue, but I think we could get around this by changing the default log level in the |
@undertome, yup, I saw those too. Much of the noise from |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, and removes a lot of extra output. For reference, here's what's left after I strip out all the test names. That's about 150 fewer lines of extra output from develop
.
7> -- Msg: max redirects
7> -- Msg: max redirects
7> -- Msg: max redirects
7> -- Msg: max redirects
7> -- Msg: max redirects
7> -- Msg: Unsupported scheme: 'ftp'
7> -- Msg: file URI cannot contain a hostname
7> -- Msg: bad json
7> -- Msg: bad json
7> -- Msg: bad result code
7> -- Msg: missing location
7> -- Msg: missing fields
7> -- Msg: missing fields
7> -- Msg: fetch error
7> -- Msg: missing fields
7> -- Msg: missing fields
7> -- Msg: missing fields
14> expected_probe_count_min: 10
expected_probe_count_max: 10
7> -- Msg: max redirects
7> -- Msg: max redirects
7> -- Msg: max redirects
7> -- Msg: max redirects
7> -- Msg: max redirects
7> -- Msg: Unsupported scheme: 'ftp'
7> -- Msg: file URI cannot contain a hostname
7> -- Msg: bad json
7> -- Msg: bad json
7> -- Msg: bad result code
7> -- Msg: missing location
7> -- Msg: missing fields
7> -- Msg: missing fields
7> -- Msg: fetch error
7> -- Msg: missing fields
7> -- Msg: missing fields
7> -- Msg: missing fields
7> -- Msg: bad json
7> -- Msg: fetch error
7> -- Msg: fetch error
7> Skipping rm dir: test_fetch1
11> 2E81FC6EC0DD943197E0C7E3FBE9AE307F2775F2F7485BB37307984C3C0F23409ED78915C6325F2EC67182FC916040556592DEDF7E8EEF67686570D4B2CC3053437CFC44ED39E3E58650C80C023EB01B7AA4E5E20BBF61A8A59FC2A711A38BEB11> ripple.app.PayStrand To Strand
12> Skipping rm dir: test_db1
12> Skipping rm dir: test_cfg6
12> Skipping rm dir: test_cfg7
12> Skipping rm dir: test_cfg8
Loading: "testSetup12\rippled.cfg"
12> Skipping rm dir: test_cfg9
12> Skipping rm dir: test_cfg9
Loading: "testSetup12\rippled.cfg"
Loading: "testSetup13\rippled.cfg"
Loading: "testSetup13\rippled.cfg"
12> Opened '' (ip=127.0.0.1:0, http)
12> server listening on port 60946
12> #1 accept: 127.0.0.1
12> #1 destroyed: 1 request
12> #2 accept: 127.0.0.1
12> #2 destroyed: 2 requests
10> [server] up on port: 51972
template_mismatch: Field 'Account' is required but missing.
template_mismatch: Field 'SignerWeight' is required but missing.
template_mismatch: Field 'Amount' found in disallowed location.
template_mismatch: Field 'Account' is required but missing.
15> Checking destination invariants...
@undertome, I've reduced the unit test noise further by removing some logging that I found I the unit tests. |
Thanks for the review @undertome. @ximinez, do you want to take a second look at this pull request since I added a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still looks good
Context of Change
A few unit tests have historically generated noise to the console caused by log writes. This noise was not useful and made it harder to locate actual test failures.
By changing the log level of these tests from
severities::kError
toseverities::kDisabled
it was possible to remove that noise coming from the logs.
Only those unit tests currently producing log noise were changed. This is so, in the future, we can see if pre-existing unit tests start producing unexpected log noise.
Type of Change