Yuck :-(... thank you for handling this.
Gary
On Fri, May 1, 2015 at 11:03 AM, Ralph Goers
wrote:
> I have a Jira issue open for this. I had them upgrade Maven after we
> upgraded the site plugin version. Unfortunately the latest Maven version
> (3.3.x) is failing with some strange error. I ha
I have a Jira issue open for this. I had them upgrade Maven after we upgraded
the site plugin version. Unfortunately the latest Maven version (3.3.x) is
failing with some strange error. I haven’t had a chance to test with that
version but recommended they try using 3.2.x, which worked for me in
I have a Jira issue open for this. I had them upgrade Maven after we upgraded
the site plugin version. Unfortunately the latest Maven version (3.3.x) is
failing with some strange error. I haven’t had a chance to test with that
version but recommended they try using 3.2.x, which worked for me in
Who knows how to fix this?
Gary
Original message
From: build...@apache.org
Date: 05/01/2015 01:17 (GMT-08:00)
To: log4j-dev@logging.apache.org
Subject: buildbot exception in ASF Buildbot on log4j2-nightly
The Buildbot has detected a build exception on builder log4j2-night
That makes sense. Both declare a Marker with the same name but with different
parents. Now that I know what is causing it I think I can fix it.
Ralph
> On Nov 30, 2014, at 10:42 PM, Gary Gregory wrote:
>
> This can be reproduced by running the LoggerTest before the MarkerTest:
>
> cd log4j-s
Should be fixed in git master now.
Gary
On Mon, Dec 1, 2014 at 12:51 AM, Gary Gregory
wrote:
> You can also reproduce it this way:
>
> package org.apache.logging.slf4j;
>
> import org.junit.runner.RunWith;
> import org.junit.runners.Suite;
> import org.junit.runners.Suite.SuiteClasses;
>
> @Run
You can also reproduce it this way:
package org.apache.logging.slf4j;
import org.junit.runner.RunWith;
import org.junit.runners.Suite;
import org.junit.runners.Suite.SuiteClasses;
@RunWith(Suite.class)
@SuiteClasses({
LoggerTest.class,
MarkerTest.class })
public class OrderBugTes
On Mon, Dec 1, 2014 at 12:44 AM, Gary Gregory
wrote:
> The brute force way to 'fix' this is to set reuseForks to false in the
> parent POM but then we will never find leaky kinds of bugs.
>
Oh, and that would slow down the test phase a lot.
Gary
>
> Gary
>
> On Mon, Dec 1, 2014 at 12:42 AM, Ga
The brute force way to 'fix' this is to set reuseForks to false in the
parent POM but then we will never find leaky kinds of bugs.
Gary
On Mon, Dec 1, 2014 at 12:42 AM, Gary Gregory
wrote:
> This can be reproduced by running the LoggerTest before the MarkerTest:
>
> cd log4j-slf4j-impl
> mvn te
This can be reproduced by running the LoggerTest before the MarkerTest:
cd log4j-slf4j-impl
mvn test
-Dtest=org.apache.logging.slf4j.LoggerTest,org.apache.logging.slf4j.MarkerTest
Gary
On Sat, Nov 29, 2014 at 12:16 PM, Gary Gregory
wrote:
> I see this locally. It seems that a lot of tests do n
I see this locally. It seems that a lot of tests do not clean up after
themselves. So might have to run in their own VMs...
On Sat, Nov 29, 2014 at 11:58 AM, Ralph Goers
wrote:
> I am not sure why the nightly build would be building the site.
>
> Yesterday when i saw this I performed a log4j bui
I am not sure why the nightly build would be building the site.
Yesterday when i saw this I performed a log4j build and it failed with the log
below. I can’t really tell what is wrong with the MarkerTest just by looking.
T E S T S
---
Running
ah there is more info:
http://ci.apache.org/builders/log4j2-nightly/builds/177/steps/compile_1/logs/stdio
Gary
On Sat, Nov 29, 2014 at 7:18 AM, Gary Gregory
wrote:
> How can we tell what's wrong?
>
> Gary
>
>
> Original message
> From: build...@apache.org
> Date:11/29/2014 03:
:-) I completely agree.
Sent from my iPhone
> On 2014/11/29, at 21:18, Gary Gregory wrote:
>
> How can we tell what's wrong?
>
> Gary
>
>
> Original message
> From: build...@apache.org
> Date:11/29/2014 03:17 (GMT-05:00)
> To: log4j-dev@logging.apache.org
> Cc:
> Subject:
14 matches
Mail list logo
