Github user xnslong commented on the issue: https://github.com/apache/logging-log4j2/pull/92 I reappeared the failure! when I run the tests with `mvn clean test -pl log4j2-core`, I got the following failure (it is just the failure you provided) ``` [ERROR] Failures: [ERROR] AbstractStringLayoutTest.testGetStringBuilderCapacityRestrictedToMax:74 capacity, trimmed to MAX_STRING_BUILDER_SIZE expected:<2048> but was:<4096> ``` Then I run mvn in debug mode, and find out the `log4j2-api` is not my local code, but some code downloaded from the maven snapshot repository. > command for running test in debug mode: > > ``` > mvn test -pl log4j-core -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Xnoagent -Djava.compiler=NONE" -Dtest=AbstractStringLayoutTest > ``` Well, the correct command for running the test is `mvn clean test -am -pl log4j2-core`. It will compile `log4j2-core` and all its dependent modules, but I didn't have java9 installed, so it will always fail for the `log4j-api-java9`. If you have java9 installed, please check it to see whether it fails.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---