Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: Verbose logging introduced by LogCaptor #1849

Closed
wants to merge 3 commits into from
Closed

fix: Verbose logging introduced by LogCaptor #1849

wants to merge 3 commits into from

Commits on Aug 30, 2023

  1. fix: Verbose logging introduced by LogCaptor 

    Adding the LogCaptor dependency caused the logging level to be DEBUG instead of INFO, even though it is configured to be INFO in log4j2.xml. This is a known issue (Hakky54/log-captor#8) because LogCaptor uses a different appender than the one configured in log4j2.xml. More details in this comment: Hakky54/log-captor#8 (comment).

The solution is to remove the dependency and create a custom appender which is used to test the logs.
    @joc-a
    joc-a committed Aug 30, 2023
    Configuration menu
    Copy the full SHA
    7bafedf View commit details
    Browse the repository at this point in the history

  2. debug TC failure

    @joc-a
    joc-a committed Aug 30, 2023
    Configuration menu
    Copy the full SHA
    1fac540 View commit details
    Browse the repository at this point in the history

Commits on Aug 31, 2023

  1. fix: Verbose logging introduced by LogCaptor 

    Add TestAppender programmatically for one test rather than enable it for all tests.
    @joc-a
    joc-a committed Aug 31, 2023
    Configuration menu
    Copy the full SHA
    62d284c View commit details
    Browse the repository at this point in the history