mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-10-31 22:38:58 +00:00
[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 commit666b02eb9d
) (cherry picked from commitb69e4d3058
) (cherry picked from commit0c1aecd7ec
) (cherry picked from commit0304e41345
) (cherry picked from commit4bcc7e02ce
) (cherry picked from commit98364235f2
) (cherry picked from commitca465e97c1
) (cherry picked from commit653045ade1
) (cherry picked from commit9ca2e644ab
) (cherry picked from commit47c8a05b37
) (cherry picked from commit4235d929ed
) (cherry picked from commit10541c4b1c
) (cherry picked from commitc1a0e1eb2f
) (cherry picked from commitba5d0193da
) (cherry picked from commit58d0e2e138
) (cherry picked from commitd411ab911b
) (cherry picked from commit454b5d9280
) (cherry picked from commit2d6ae51745
)
This commit is contained in:
parent
59a684f038
commit
033729e91f
1 changed files with 1 additions and 1 deletions
|
@ -90,7 +90,7 @@ LEVEL = Info
|
|||
COLORIZE = true
|
||||
|
||||
[log.file]
|
||||
LEVEL = Debug
|
||||
LEVEL = Trace
|
||||
|
||||
[security]
|
||||
PASSWORD_HASH_ALGO = argon2
|
||||
|
|
Loading…
Reference in a new issue