[jira] [Commented] (LOG4J2-2613) Fix RollingAppenderSizeWithTimeTest.testAppender flakes

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865678#comment-16865678 ] 

ASF subversion and git services commented on LOG4J2-2613:
---------------------------------------------------------

Commit 7de998159e2cfb9cda0170572bc0273d1eb18b84 in logging-log4j2's branch refs/heads/release-2.x from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=7de9981 ]

LOG4J2-2613 - Attempt to eliminate test failures by requiring more logs before rollover


> 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
>            Assignee: Ralph Goers
>            Priority: Major
>             Fix For: 2.12.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)