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 Apache Jenkins Server <je...@builds.apache.org> on 2016/04/26 17:07:15 UTC
Jenkins build became unstable: Log4j 2.x #1909
See <https://builds.apache.org/job/Log4j%202.x/1909/changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Jenkins build became unstable: Log4j 2.x #1909
Posted by Remko Popma <re...@gmail.com>.
I raised this issue:
https://github.com/google/allocation-instrumenter/issues/15
Hopefully it is being maintained...
On Wed, Apr 27, 2016 at 1:23 AM, Remko Popma <re...@gmail.com> wrote:
> Yes, this looks like a bug in the Google AllocationRecorder
> <https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java>
> :
>
> The NullPointerException we are seeing occurs when a shutdown hook
> allocates a new object.
> The instrumented bytecode still invokes the recordAllocation method.
>
> The AllocationRecorder also has a shutdown hook
> <https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L49> which sets
> its instrumentation field to null.
> These shutdown hook threads run at the same time, so if the
> instrumentation field is set to null after the null check
> <https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L236>
> but before it is used in getObjectSize
> <https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L192>,
> we get the exception.
>
>
> On Wed, Apr 27, 2016 at 12:29 AM, Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> Any idea how to determine what caused this to fail?
>>
>> Ralph
>>
>> > On Apr 26, 2016, at 8:07 AM, Apache Jenkins Server <
>> jenkins@builds.apache.org> wrote:
>> >
>> > See <https://builds.apache.org/job/Log4j%202.x/1909/changes>
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >
>> >
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>
>
Re: Jenkins build became unstable: Log4j 2.x #1909
Posted by Remko Popma <re...@gmail.com>.
Yes, this looks like a bug in the Google AllocationRecorder
<https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java>
:
The NullPointerException we are seeing occurs when a shutdown hook
allocates a new object.
The instrumented bytecode still invokes the recordAllocation method.
The AllocationRecorder also has a shutdown hook
<https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L49>
which sets
its instrumentation field to null.
These shutdown hook threads run at the same time, so if the instrumentation
field is set to null after the null check
<https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L236>
but before it is used in getObjectSize
<https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L192>,
we get the exception.
On Wed, Apr 27, 2016 at 12:29 AM, Ralph Goers <ra...@dslextreme.com>
wrote:
> Any idea how to determine what caused this to fail?
>
> Ralph
>
> > On Apr 26, 2016, at 8:07 AM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
> >
> > See <https://builds.apache.org/job/Log4j%202.x/1909/changes>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
Re: Jenkins build became unstable: Log4j 2.x #1909
Posted by Matt Sicker <bo...@gmail.com>.
Do you mean this?
https://builds.apache.org/job/Log4j%202.x/1909/org.apache.logging.log4j$log4j-core/testReport/org.apache.logging.log4j.core/GcFreeMixedSyncAyncLoggingTest/testNoAllocationDuringSteadyStateLogging/
On 26 April 2016 at 10:29, Ralph Goers <ra...@dslextreme.com> wrote:
> Any idea how to determine what caused this to fail?
>
> Ralph
>
> > On Apr 26, 2016, at 8:07 AM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
> >
> > See <https://builds.apache.org/job/Log4j%202.x/1909/changes>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> 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 #1909
Posted by Ralph Goers <ra...@dslextreme.com>.
Any idea how to determine what caused this to fail?
Ralph
> On Apr 26, 2016, at 8:07 AM, Apache Jenkins Server <je...@builds.apache.org> wrote:
>
> See <https://builds.apache.org/job/Log4j%202.x/1909/changes>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Jenkins build is back to stable : Log4j 2.x #1912
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Log4j%202.x/1912/>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Jenkins build is still unstable: Log4j 2.x #1911
Posted by Remko Popma <re...@gmail.com>.
This is our old friend bz2.
Sent from my iPhone
> On 2016/04/27, at 8:05, Apache Jenkins Server <je...@builds.apache.org> wrote:
>
> See <https://builds.apache.org/job/Log4j%202.x/changes>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Jenkins build is still unstable: Log4j 2.x #1911
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Log4j%202.x/changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Jenkins build is still unstable: Log4j 2.x #1910
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Log4j%202.x/changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org