From ca465e97c1b5d1db684cf9fa1ecbaa14f4bb077c Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Fri, 21 Jul 2023 07:35:52 +0200 Subject: [PATCH] [TESTS] increase test-sqlite log level to Trace It does not pollute the output because they go to sqlite-log/gitea.log and it may provide clues for debugging. When trying to figure out a problem in production, Debug is likely to be used but in a development environment a very fine grain log is the most useful. If that's really too much noise, the lines can be trimmed by removing all those with [T]. (cherry picked from commit 666b02eb9d6e50b3a8d3ec5659fa6fb8451d0d9f) (cherry picked from commit b69e4d30581258d82d9b2a4daf932f75d7d7171e) (cherry picked from commit 0c1aecd7ec0d3bf9801c02ae24c89dd5ce074255) (cherry picked from commit 0304e41345e8ab19537d3686b5487c8cb4b280c2) (cherry picked from commit 4bcc7e02ce496bea54de39d1059cf39617d2a8d9) (cherry picked from commit 98364235f2792ce058984c03dde2f609adfbfc88) --- tests/sqlite.ini.tmpl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/sqlite.ini.tmpl b/tests/sqlite.ini.tmpl index 9ed4ab0e99..dde2f2017c 100644 --- a/tests/sqlite.ini.tmpl +++ b/tests/sqlite.ini.tmpl @@ -90,7 +90,7 @@ LEVEL = Info COLORIZE = true [log.file] -LEVEL = Debug +LEVEL = Trace [security] PASSWORD_HASH_ALGO = argon2