go-ethereum

Commit Graph

Author	SHA1	Message	Date
jwasinger	984f82629c	cmd/geth: more special cases logging tests (#28527 ) adds logging tests for errors and custom fmt.Stringer-types which output strings that needs to be quoted/escaped.	10 months ago
Martin Holst Swende	b77a9b127c	cmd/geth: more testcases for logging (#28501 ) * cmd/geth: more testcases for logging This adds more edgecases around logging, particularly around handling of different types of nil-values as concrete types and within interfaces. Also adds tests with 'reserved' values which breaks json/logfmt formats. The json output is checked in, but not actively used by any testcase at the moment. * cmd/geth/testdata: remove timestamps	11 months ago
Martin Holst Swende	58ae1df684	cmd/geth: test for logging-output (#28373 ) This PR is a bit in preparation for the slog work in #28187 . Our current test re logging mostly test the internals, but we have no real end-to-end test of the logging output. This PR introduces a simple reexec-based log tester. This also relies upon a special mode in geth, which can be made to eject a set of predefined log messages (only available if the build-tag `integrationtests` is used e.g. go run --tags=integrationtests ./cmd/geth --log.format terminal logtest While working on this, I also noticed a quirk in the setup: when geth was configured to use a file output, then two separate handlers were used (one handler for the file, one handler for the console). Using two separate handlers means that two formatters are used, thus the formatting of any/all records happened twice. This PR changes the mechanism to use two separate io.Writers instead, which is both more optimal and fixes a bug which occurs due to a global statefulness in the formatter.	11 months ago

Author

SHA1

Message

Date

jwasinger

984f82629c

cmd/geth: more special cases logging tests (#28527 )

adds logging tests for errors and custom fmt.Stringer-types which output strings that needs to be quoted/escaped.

10 months ago

Martin Holst Swende

b77a9b127c

cmd/geth: more testcases for logging (#28501 )

* cmd/geth: more testcases for logging

This adds more edgecases around logging, particularly around handling of different types of nil-values
as concrete types and within interfaces.

Also adds tests with 'reserved' values which breaks json/logfmt formats. The json output is checked in,
but not actively used by any testcase at the moment.

* cmd/geth/testdata: remove timestamps

11 months ago

Martin Holst Swende

58ae1df684

cmd/geth: test for logging-output (#28373 )

This PR is a bit in preparation for the slog work in #28187 .

Our current test re logging mostly test the internals, but we have no real end-to-end test of the logging output. This PR introduces a simple reexec-based log tester. This also relies upon a special mode in geth, which can be made to eject a set of predefined log messages (only available if the build-tag `integrationtests` is used

e.g. go run --tags=integrationtests ./cmd/geth --log.format terminal logtest

While working on this, I also noticed a quirk in the setup: when geth was configured to use a file output, then two separate handlers were used (one handler for the file, one handler for the console). Using two separate handlers means that two formatters are used, thus the formatting of any/all records happened twice. This PR changes the mechanism to use two separate io.Writers instead, which is both more optimal and fixes a bug which occurs due to a global statefulness in the formatter.

11 months ago

3 Commits (34dcd749355f161f1ed7efe9e59c6c9d13402ff6)