[
https://issues.apache.org/jira/browse/LOG4J2-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846772#comment-16846772
]
ASF subversion and git services commented on LOG4J2-2613:
---------------------------------------------------------
Commit 7a3282d097f37f5f06d7a9e1a3406e776132586b in logging-log4j2's branch
refs/heads/master from Carter Kozak
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=7a3282d ]
LOG4J2-2613: Ignore RollingAppenderSizeWithTimeTest.testAppender
Ignoring the test as a temporary measure to give other builds
a chance to succeed.
This test causes most travis builds to flake. Failures can be
reproduced locally, though at a much lower rate.
> Fix RollingAppenderSizeWithTimeTest.testAppender flakes
> -------------------------------------------------------
>
> Key: LOG4J2-2613
> URL: https://issues.apache.org/jira/browse/LOG4J2-2613
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Reporter: Carter Kozak
> Priority: Major
> Fix For: 2.12.0
>
>
> This test was introduced a week or two ago in
> [https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;a=commit;h=619707edd57fd6f562ea154d1eac56708b6634e2]
> I can reproduce the failure locally by creating a junit suite which repeats
> the RollingAppenderSizeWithTimeTest class. Using ten runs I have been able to
> trigger every time on my local machine.
> This failure may be related to LOG4J2-2610 based on github PR comments here:
> [https://github.com/apache/logging-log4j2/pull/271]
> I will temporarily ignore this test to allow other builds to complete, we
> should not release until we've had a chance to resolve the failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
