tendermint

bft blockchain consensus consistency cryptocurrency cryptography db distributed-systems go

History

Sam Kleinman 0bded371c5 testing: logger cleanup (#8153 ) This contains two major changes: - Remove the legacy test logging method, and just explicitly call the noop logger. This is just to make the test logging behavior more coherent and clear. - Move the logging in the light package from the testing.T logger to the noop logger. It's really the case that we very rarely need/want to consider test logs unless we're doing reproductions and running a narrow set of tests. In most cases, I (for one) prefer to run in verbose mode so I can watch progress of tests, but I basically never need to consider logs. If I do want to see logs, then I can edit in the testing.T logger locally (which is what you have to do today, anyway.)	2 years ago
..
event_bus.go	node: pass eventbus at construction time (#8084)	2 years ago
event_bus_test.go	testing: logger cleanup (#8153)	2 years ago

This contains two major changes:

- Remove the legacy test logging method, and just explicitly call the
  noop logger. This is just to make the test logging behavior more
  coherent and clear. 
  
- Move the logging in the light package from the testing.T logger to
  the noop logger. It's really the case that we very rarely need/want
  to consider test logs unless we're doing reproductions and running a
  narrow set of tests.
  
In most cases, I (for one) prefer to run in verbose mode so I can
watch progress of tests, but I basically never need to consider
logs. If I do want to see logs, then I can edit in the testing.T
logger locally (which is what you have to do today, anyway.)

2 years ago

event_bus.go

node: pass eventbus at construction time (#8084)

2 years ago

event_bus_test.go

testing: logger cleanup (#8153)

2 years ago