-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
3
-
Storage Engines - 2022-12-12
Summary
There are too many messages printed out from test_cursor_bound_fuzz. See this patch build that executed the unit-test task.
Those messages come from the following calls:
self.printVerbose(2, ...)
Motivation
- Is this issue urgent?
No
Acceptance Criteria (Definition of Done)
Those logs don't show up when executing the tests on Evergreen.
Suggested Solution
Either change the level of those calls to 3 or do not use level 2 when executing the Python tests in Evergreen. The Evergreen command for those tests is currently:
${test_env_vars|} ${python_binary|python3} ../test/suite/run.py ${unit_test_args|-v 2} ${smp_command|} 2>&1
On a side note, I noticed we use both the APIs self.verbose and self.printVerbose is Python. I believe we could get rid of one or the other.
- duplicates
-
WT-9982 Change test_cursor_bound_fuzz verbose logging level
- Closed