You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Matt Sicker <bo...@gmail.com> on 2016/07/04 19:15:16 UTC
Re: Jenkins build became unstable: Log4j 2.x #2085
New test failure: RollingAppenderCronTest.
On 4 July 2016 at 14:03, Apache Jenkins Server <je...@builds.apache.org>
wrote:
> See <https://builds.apache.org/job/Log4j%202.x/2085/changes>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
Matt Sicker <bo...@gmail.com>
Re: Jenkins build became unstable: Log4j 2.x #2085
Posted by Ralph Goers <ra...@dslextreme.com>.
Yup. I just added some more logging to help identify the problem.
Ralph
> On Jul 4, 2016, at 12:15 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> New test failure: RollingAppenderCronTest.
>
> On 4 July 2016 at 14:03, Apache Jenkins Server <jenkins@builds.apache.org <ma...@builds.apache.org>> wrote:
> See <https://builds.apache.org/job/Log4j%202.x/2085/changes <https://builds.apache.org/job/Log4j%202.x/2085/changes>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org <ma...@logging.apache.org>
> For additional commands, e-mail: log4j-dev-help@logging.apache.org <ma...@logging.apache.org>
>
>
>
>
> --
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>