From ffff9dcdc3cbe427739cc19cc7a53f032474fa2a Mon Sep 17 00:00:00 2001 From: MarcoFalke Date: Mon, 9 Mar 2020 14:40:47 -0400 Subject: test: Explain why test logging should be used --- test/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/README.md') diff --git a/test/README.md b/test/README.md index c3e4ae9ad2..e1dab92a06 100644 --- a/test/README.md +++ b/test/README.md @@ -145,7 +145,7 @@ levels using the logger included in the test_framework, e.g. `test_framework.log` and no logs are output to the console. - when run directly, *all* logs are written to `test_framework.log` and INFO level and above are output to the console. -- when run on Travis, no logs are output to the console. However, if a test +- when run by [our CI (Continuous Integration)](/ci/README.md), no logs are output to the console. However, if a test fails, the `test_framework.log` and bitcoind `debug.log`s will all be dumped to the console to help troubleshooting. -- cgit v1.2.3