aboutsummaryrefslogtreecommitdiff
path: root/test/README.md
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2020-03-09 14:40:47 -0400
committerMarcoFalke <falke.marco@gmail.com>2020-03-10 08:24:49 -0400
commitffff9dcdc3cbe427739cc19cc7a53f032474fa2a (patch)
tree94532e3a233b42f169dee03a22f4bfc104ccf8f4 /test/README.md
parent5518eeec2727d40e1105901a8751bf584ab69402 (diff)
downloadbitcoin-ffff9dcdc3cbe427739cc19cc7a53f032474fa2a.tar.xz
test: Explain why test logging should be used
Diffstat (limited to 'test/README.md')
-rw-r--r--test/README.md2
1 files changed, 1 insertions, 1 deletions
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.