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/04/18 16:19:55 UTC
Re: Jenkins build became unstable: Log4j 2.x #1885
That's a strange test result!
On 18 April 2016 at 09:05, Apache Jenkins Server <je...@builds.apache.org>
wrote:
> See <https://builds.apache.org/job/Log4j%202.x/1885/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 #1885
Posted by Remko Popma <re...@gmail.com>.
I updated the GcFreeLogging tests to stop paying attention to allocations
that occur after the test is complete. That should fix this.
On Mon, Apr 18, 2016 at 11:37 PM, Remko Popma <re...@gmail.com> wrote:
> Looks like the JUL LogManager.Clearer class (their shutdown hook)
> allocates while looping over a map.
>
> The thing is, I call
>
> AllocationRecorder.removeSampler(sampler);
> Thread.sleep(100);
>
> before exiting the test process... Looks like the AllocationRecorder is
> still active. Hm...
>
>
> On Mon, Apr 18, 2016 at 11:19 PM, Matt Sicker <bo...@gmail.com> wrote:
>
>> That's a strange test result!
>>
>> On 18 April 2016 at 09:05, Apache Jenkins Server <
>> jenkins@builds.apache.org> wrote:
>>
>>> See <https://builds.apache.org/job/Log4j%202.x/1885/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 #1885
Posted by Remko Popma <re...@gmail.com>.
Looks like the JUL LogManager.Clearer class (their shutdown hook) allocates
while looping over a map.
The thing is, I call
AllocationRecorder.removeSampler(sampler);
Thread.sleep(100);
before exiting the test process... Looks like the AllocationRecorder is
still active. Hm...
On Mon, Apr 18, 2016 at 11:19 PM, Matt Sicker <bo...@gmail.com> wrote:
> That's a strange test result!
>
> On 18 April 2016 at 09:05, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
>> See <https://builds.apache.org/job/Log4j%202.x/1885/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>
>