[
https://issues.apache.org/jira/browse/LOG4J2-2613?focusedWorklogId=261042&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261042
]
ASF GitHub Bot logged work on LOG4J2-2613:
------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jun/19 18:36
Start Date: 16/Jun/19 18:36
Worklog Time Spent: 10m
Work Description: carterkozak commented on pull request #277: Suite to
reproduce LOG4J2-2613 test flakes
URL: https://github.com/apache/logging-log4j2/pull/277
----------------------------------------------------------------
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 service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 261042)
Time Spent: 10m
Remaining Estimate: 0h
> 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)
