[CI][UNSTABLE] Logging/log4j/master#247 has test failures

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/247/ Project: master Date of build: Wed, 24 Mar 2021 19:29:14 + Build duration: 1 hr 24 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2 Failed:

[GitHub] [logging-log4j2] carterkozak closed pull request #479: LOG4J2-2940 StackWalker optimization and avoidance

carterkozak closed pull request #479: URL: https://github.com/apache/logging-log4j2/pull/479 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this servic

[GitHub] [logging-log4j2] carterkozak commented on pull request #479: LOG4J2-2940 StackWalker optimization and avoidance

carterkozak commented on pull request #479: URL: https://github.com/apache/logging-log4j2/pull/479#issuecomment-806164744 merged -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comm

[jira] [Commented] (LOG4J2-2940) High CPU at Java 11 due to the use of StackWalker from StackLocator.getCallerClass

[ https://issues.apache.org/jira/browse/LOG4J2-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308149#comment-17308149 ] ASF subversion and git services commented on LOG4J2-2940: - Commi

[jira] [Commented] (LOG4J2-2940) High CPU at Java 11 due to the use of StackWalker from StackLocator.getCallerClass

[ https://issues.apache.org/jira/browse/LOG4J2-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308145#comment-17308145 ] ASF subversion and git services commented on LOG4J2-2940: - Commi

[jira] [Commented] (LOG4J2-2940) High CPU at Java 11 due to the use of StackWalker from StackLocator.getCallerClass

[ https://issues.apache.org/jira/browse/LOG4J2-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308141#comment-17308141 ] ASF subversion and git services commented on LOG4J2-2940: - Commi

[jira] [Commented] (LOG4J2-2940) High CPU at Java 11 due to the use of StackWalker from StackLocator.getCallerClass

[ https://issues.apache.org/jira/browse/LOG4J2-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308142#comment-17308142 ] ASF subversion and git services commented on LOG4J2-2940: - Commi

[jira] [Closed] (LOG4J2-3054) BasicContextSelector.hasContext should take default CONTEXT into account

[ https://issues.apache.org/jira/browse/LOG4J2-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Barsov closed LOG4J2-3054. - > BasicContextSelector.hasContext should take default CONTEXT into account > ---

[jira] [Commented] (LOG4J2-3054) BasicContextSelector.hasContext should take default CONTEXT into account

[ https://issues.apache.org/jira/browse/LOG4J2-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307756#comment-17307756 ] Alexey Barsov commented on LOG4J2-3054: --- yes, the issue issue is gone in 2.15.0-SN

[jira] [Closed] (LOG4J2-2952) How can I do the same thing using log4j2 like what I did when using logback with janino?

[ https://issues.apache.org/jira/browse/LOG4J2-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Liu closed LOG4J2-2952. - sorry for the delay > How can I do the same thing using log4j2 like what I did when using logback > with j