It's from an async test. Could be a timing issue. I'd wait to see if it
pops up again.

On 14 August 2017 at 15:58, Ralph Goers <[email protected]> wrote:

>
> I don’t recall having seen this error before. Did the latest commit break
> something?
>
> Ralph
>
> > On Aug 14, 2017, at 1:12 PM, Apache Jenkins Server <
> [email protected]> wrote:
> >
> > See <https://builds.apache.org/job/Log4j%202.x/2980/display/
> redirect?page=changes>
> >
> >
>
>
>


-- 
Matt Sicker <[email protected]>

Reply via email to