See <https://builds.apache.org/job/Log4j%202%203.x/541/display/redirect?page=changes>
Changes: [rgoers] LOG4J2-2211 - Allow Lookup keys with leading dashes by using a slash as ------------------------------------------ Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu) in workspace <https://builds.apache.org/job/Log4j%202%203.x/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url > https://gitbox.apache.org/repos/asf/logging-log4j2.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Fetching upstream changes from https://gitbox.apache.org/repos/asf/logging-log4j2.git > git --version # timeout=10 > git fetch --tags --progress -- > https://gitbox.apache.org/repos/asf/logging-log4j2.git > +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision 19aa7fd40606d728471953890f86c9ae4d88ea5b (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 19aa7fd40606d728471953890f86c9ae4d88ea5b Commit message: "LOG4J2-2211 - Allow Lookup keys with leading dashes by using a slash as an escape character." > git rev-list --no-walk b74f92cbf1e7107b0ef637f252d752b1470c7aee # timeout=10 [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content LANG=en_US.UTF-8 [EnvInject] - Variables injected successfully. Parsing POMs Modules changed, recalculating dependency graph Established TCP socket on 46203 maven35-agent.jar already up to date maven35-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [Log4j 2 3.x] $ /home/jenkins/tools/java/latest1.8/bin/java -Xmx2g -Xms256m -XX:MaxPermSize=256m -cp /home/jenkins/jenkins-slave/maven35-agent.jar:/home/jenkins/tools/maven/latest/boot/plexus-classworlds-2.6.0.jar:/home/jenkins/tools/maven/latest/conf/logging jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/latest/ /home/jenkins/jenkins-slave/remoting.jar /home/jenkins/jenkins-slave/maven35-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 46203 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 # # There is insufficient memory for the Java Runtime Environment to continue. # Cannot create GC thread. Out of system resources. # An error report file with more information is saved as: # <https://builds.apache.org/job/Log4j%202%203.x/ws/hs_err_pid20279.log> ERROR: Failed to launch Maven. Exit code = 1