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.
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
Banner printed 4 times with log4j2 #3186
Comments
It might happen if you are running tests in parallel. |
How can I control if tests are executed in parallel or not? I have tried the following but still have the same output: $ /usr/local/bin/mvn -v
Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
Maven home: /usr/local/Cellar/maven/3.9.2/libexec
Java version: 17.0.6, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
Default locale: en_GB, platform encoding: UTF-8
OS name: "mac os x", version: "12.6.7", arch: "x86_64", family: "mac"
$ /usr/local/bin/mvn clean install -DforkCount=1 -Dparallel=none
… |
I am also getting this issue. My tests are not running in Parallel mode. |
I use serenity 4.0.5, gradle + junit5 implementation "ch.qos.logback:logback-classic:$logback_version"
implementation "ch.qos.logback:logback-core:$logback_version"
implementation "org.slf4j:slf4j-api:$slf4j_version"
implementation "org.slf4j:slf4j-jdk14:$slf4j_version"
implementation "org.slf4j:log4j-over-slf4j:$slf4j_version" I run tests in single thread, no parallel mode at all. In logs I see that banner is printed 3 times at the beginning, then every Serenity log entry ( |
Just wanted to confirm I cannot reproduce the issue with version 4.0.12. Thanks! |
Hello,
I created an example project, using log4j2 as the logging framework with a basic log4j2.xml config: https://git.sr.ht/~nyg/example-java-serenity.
When I run
mvn clean install
, the Serenity banner is printed 4 times while the “Test started” is printed twice.Is this a bug or an issue with my log4j2 config?
Thanks,
nyg
log4j2.xml
mvn clean install
By the way, I think #3114 can be closed.
The text was updated successfully, but these errors were encountered: