From ff3be6f335e5148524ed6ddd6bf59a667b73ac20 Mon Sep 17 00:00:00 2001 From: zeripath Date: Sun, 7 Apr 2019 01:25:14 +0100 Subject: [PATCH] Quieter Integration Tests (#6513) * Rename BaseLogger to WriterLogger to help the creation of other providers * Don't export ColorBytes and ResetBytes from ColoredValues * Make integration tests only print logs if they fail * check can color before coloring * I always forget about MSSQL * Oh and use LEVEL in sqlite.ini * Make the test logger log at info - as it means you see the router * Remove empty expected changes * Make the migrations quieter too * Don't display SQL on error - it can be looked at in the file logs if necessary * Fix skip when using onGiteaRun --- doc/advanced/logging-documentation.en-us.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/advanced/logging-documentation.en-us.md b/doc/advanced/logging-documentation.en-us.md index db8dcbba..bef034e2 100644 --- a/doc/advanced/logging-documentation.en-us.md +++ b/doc/advanced/logging-documentation.en-us.md @@ -357,10 +357,10 @@ attributes should be cached if this is a commonly used log message. of bytes representing the color. These functions will not double wrap a `log.ColoredValue`. They will -also set the ResetBytes to the cached resetBytes. +also set the `resetBytes` to the cached `resetBytes`. -Be careful not to change the contents of resetBytes or boldBytes as this -will break rendering of logging elsewhere. You have been warned. +The `colorBytes` and `resetBytes` are not exported to prevent +accidental overwriting of internal values. ## Log Spoofing protection