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 2017/01/03 22:12:45 UTC
Jenkins build became unstable: Log4j 2.x #2564
See <https://builds.apache.org/job/Log4j%202.x/2564/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 back to stable : Log4j 2.x #2567
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Log4j%202.x/2567/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 #2566
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
Re: Jenkins build is still unstable: Log4j 2.x #2565
Posted by Matt Sicker <bo...@gmail.com>.
Reverted 1763. It appears that we cannot rely on MethodHandle in a caller
sensitive method like getCallerClass(int) due to a bug in JDK 7 (works fine
in JDK 8, however). There may be a way to support this in JDK 8
environments only, though.
On 3 January 2017 at 22:34, Matt Sicker <bo...@gmail.com> wrote:
> I'm working on creating an OpenJDK 7 Dockerfile to test this. If JDK 7
> can't use MethodHandle properly, then I'll have to revert LOG4J2-1763.
>
> On 3 January 2017 at 22:26, Matt Sicker <bo...@gmail.com> wrote:
>
>> Ok, this is weird. I don't get this error locally. Is this a bug in JDK 7
>> or something?
>>
>> On 3 January 2017 at 22:15, Apache Jenkins Server <
>> jenkins@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
>>>
>>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
Matt Sicker <bo...@gmail.com>
Re: Jenkins build is still unstable: Log4j 2.x #2565
Posted by Matt Sicker <bo...@gmail.com>.
I'm working on creating an OpenJDK 7 Dockerfile to test this. If JDK 7
can't use MethodHandle properly, then I'll have to revert LOG4J2-1763.
On 3 January 2017 at 22:26, Matt Sicker <bo...@gmail.com> wrote:
> Ok, this is weird. I don't get this error locally. Is this a bug in JDK 7
> or something?
>
> On 3 January 2017 at 22:15, Apache Jenkins Server <
> jenkins@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
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
Matt Sicker <bo...@gmail.com>
Re: Jenkins build is still unstable: Log4j 2.x #2565
Posted by Matt Sicker <bo...@gmail.com>.
Ok, this is weird. I don't get this error locally. Is this a bug in JDK 7
or something?
On 3 January 2017 at 22:15, Apache Jenkins Server <jenkins@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
>
>
--
Matt Sicker <bo...@gmail.com>
Jenkins build is still unstable: Log4j 2.x #2565
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
Re: Jenkins build became unstable: Log4j 2.x #2564
Posted by Matt Sicker <bo...@gmail.com>.
I'm actually kind of wondering how useful it is to run this integration
test on Jenkins. The chances of port 9042 being open are pretty random.
On 3 January 2017 at 16:12, Apache Jenkins Server <jenkins@builds.apache.org
> wrote:
> See <https://builds.apache.org/job/Log4j%202.x/2564/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>