)
> Cassendra's integration test fails on Windows
> -
>
> Key: LOG4J2-1850
> URL: https://issues.apache.org/jira/browse/LOG4J2-1850
> Project: Log4j 2
> Issue Type: Bug
&g
verify and close. Hopefully
this means that the [Windows Jenkins
jobs|https://builds.apache.org/job/Log4jWindows/] will be fully functional now.
> Cassendra's integration test fails on Windows
> -
>
>
, so this patch
prevents calls to System.exit() while stopping the daemon.
> Cassendra's integration test fails on Windows
> -
>
> Key: LOG4J2-1850
> URL: https://issues.apache.org/jira/browse/LOG4J2-1850
&
[
https://issues.apache.org/jira/browse/LOG4J2-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker reassigned LOG4J2-1850:
---
Assignee: Matt Sicker
> Cassendra's integration test fails on
should be better
> Cassendra's integration test fails on Windows
> -
>
> Key: LOG4J2-1850
> URL: https://issues.apache.org/jira/browse/LOG4J2-1850
> Project: Log4j 2
> Is
[
https://issues.apache.org/jira/browse/LOG4J2-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ludovic HOCHET updated LOG4J2-1850:
---
Attachment: (was: patch-log4j2-1850.diff)
> Cassendra's integration test
his patch file properly. Could you use the
output from {{git format-patch}}? Or a pull request would work, too. Thanks for
figuring out why this was failing!
> Cassendra's integration test fails on Windows
> -
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ludovic HOCHET updated LOG4J2-1850:
---
Attachment: (was: patch-log4j2-1850.diff)
> Cassendra's integration test
().
> Cassendra's integration test fails on Windows
> -
>
> Key: LOG4J2-1850
> URL: https://issues.apache.org/jira/browse/LOG4J2-1850
> Project: Log4j 2
> Issue Type: Bug
&g
().)
> Cassendra's integration test fails on Windows
> -
>
> Key: LOG4J2-1850
> URL: https://issues.apache.org/jira/browse/LOG4J2-1850
> Project: Log4j 2
> Issue Type: Bug
&g
().
> Cassendra's integration test fails on Windows
> -
>
> Key: LOG4J2-1850
> URL: https://issues.apache.org/jira/browse/LOG4J2-1850
> Project: Log4j 2
> Issue Type: Bug
&g
Ludovic HOCHET created LOG4J2-1850:
--
Summary: Cassendra's integration test fails on Windows
Key: LOG4J2-1850
URL: https://issues.apache.org/jira/browse/LOG4J2-1850
Project: Log4j 2
oot module test
> suites
> --
>
> Key: LOG4J2-1777
> URL: https://issues.apache.org/jira/browse/LOG4J2-1777
> Project: Log4j 2
> Issue Type: Te
Our JUnit rule org.apache.logging.log4j.junit.CleanFiles would come in
handy here.
Gary
-- Forwarded message --
From:
Date: Tue, Jan 10, 2017 at 7:17 AM
Subject: logging-log4j2 git commit: Fix failing unit test
To: [email protected]
Repository: logging-log4j2
Updated
/Categories] to the
various integration tests that correspond to Log4j Boot modules. Also add test
suites to log4j-boot modules themselves to run those tests as part of their
build. (was: Add JUnit {{@Category}}
[annotations|https://github.com/junit-team/junit4/wiki/Categories] to the
various
[
https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-1777:
Summary: Add JUnit categories to integration tests for use in log4j-boot
module test suites (was
ter module
> test suites
> -
>
> Key: LOG4J2-1777
> URL: https://issues.apache.org/jira/browse/LOG4J2-1777
> Project: Log4j 2
> Issue Type: Te
Matt Sicker created LOG4J2-1777:
---
Summary: Add JUnit categories to integration tests for use in
log4j-starter module test suites
Key: LOG4J2-1777
URL: https://issues.apache.org/jira/browse/LOG4J2-1777
I should have said API module.
Gary
On Sun, Nov 13, 2016 at 5:10 PM, Gary Gregory
wrote:
> OK, we now have a build on Travis CI:
>
> https://travis-ci.org/apache/logging-log4j2
>
> The Core module fails on OSGi tests as it fails on my machine. I do not
> see how Jenkins passes then.
>
> I will
OK, we now have a build on Travis CI:
https://travis-ci.org/apache/logging-log4j2
The Core module fails on OSGi tests as it fails on my machine. I do not see
how Jenkins passes then.
I will @Ignore these tests for now.
Gary
--
E-Mail: [email protected] | [email protected]
Java Persiste
ugh this issue
page properly (or at all).
What my proposal fixes is the issue described on Stack Overflow. I don't know
if there's already a log4j bug record for this.
> Failover appender throws "Error flushing stream
> //L-Computer1/test/logs/primary.log" at the
27;m also not really seeing how it
relates.
> Failover appender throws "Error flushing stream
> //L-Computer1/test/logs/primary.log" at the time of retry,
ppender throws "Error flushing stream
> //L-Computer1/test/logs/primary.log" at the time of retry, but the location
> is up
> -
>
>
rror is in the {{visit()}} method of
{{PluginElementVisitor}}, line 66 (in 2.7). The array object is returned
_without_ removing the associated node from the list (as in line 79).
> Failover appender throws "Error flushing stream
> //L-Computer1/test/logs/primary.log" at the ti
I think this is better:
@Ignore("TODO fix LOG4J2-1313")
Than:
@Ignore() // TODO fix LOG4J2-1313
So I've change it.
Presumably some tooling could pick this up.
Gary
On Sun, Sep 11, 2016 at 10:06 AM, Remko Popma wrote:
> This test is for LOG4J2-1313
> <https://issue
This test is for LOG4J2-1313
<https://issues.apache.org/jira/browse/LOG4J2-1313>.
I've @ignored it for now.
On Mon, Sep 12, 2016 at 1:41 AM, Gary Gregory
wrote:
> With git master, I get:
>
> Failed tests:
> PropertyTest.testEmptyAttribute:60 expected:<1=elementValue
With git master, I get:
Failed tests:
PropertyTest.testEmptyAttribute:60
expected:<1=elementValue,2=[,3=attributeValue,4=attributeValue2,5=attribute]Value3,m=msg>
but
was:<1=elementValue,2=[${sys:emptyElementKey},3=attributeValue,4=attributeValue2,5=element]Value3,m=msg>
Tests run: 1334, Failur
free to reopen if
it's still a problem for you.
> Can not build Log4j from git master due to a test failure in Log4j Core
> ---
>
> Key: LOG4J2-1247
> URL: https://issues.apac
Gary Gregory created LOG4J2-1551:
Summary: Update JMS test from ActiveMQ 5.13.4 to 5.14.0.
Key: LOG4J2-1551
URL: https://issues.apache.org/jira/browse/LOG4J2-1551
Project: Log4j 2
Issue Type
[
https://issues.apache.org/jira/browse/LOG4J2-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1551.
Resolution: Fixed
Local build OK.
In Git master.
> Update JMS test from ActiveMQ 5.13.4
ote:
>
> Clear ThreadContext after test
>
>
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/a40b28f2
> Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/a40b28f2
> Diff: h
[
https://issues.apache.org/jira/browse/LOG4J2-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1497.
Resolution: Fixed
In Git master.
> Update JMS test from ActiveMQ 5.13.3 to 5.1
Gary Gregory created LOG4J2-1497:
Summary: Update JMS test from ActiveMQ 5.13.3 to 5.13.4
Key: LOG4J2-1497
URL: https://issues.apache.org/jira/browse/LOG4J2-1497
Project: Log4j 2
Issue Type
[
https://issues.apache.org/jira/browse/LOG4J2-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Helger closed LOG4J2-690.
> log4j-web pom.xml - test artifacts should be in test sc
On Wed, Jun 29, 2016 at 1:17 PM, Matt Sicker wrote:
> Plus it would be easier to just use LoggerContextRule here.
>
+1!
Gary
>
> On 29 June 2016 at 15:01, Gary Gregory wrote:
>
>> Almost -1: The test does not clean up after itself, specifically it does
>> not
Plus it would be easier to just use LoggerContextRule here.
On 29 June 2016 at 15:01, Gary Gregory wrote:
> Almost -1: The test does not clean up after itself, specifically it does
> not restore the system property.
>
> Gary
>
> -- Forwarded message --
> Fr
Almost -1: The test does not clean up after itself, specifically it does
not restore the system property.
Gary
-- Forwarded message --
From:
Date: Wed, Jun 29, 2016 at 12:39 PM
Subject: logging-log4j2 git commit: Incomplete test to illustrate
LOG4J2-1452
To: comm
hmarks.jar -l
On Tue, May 10, 2016 at 10:44 PM, Ralph Goers
wrote:
> I am trying to run the location test and am getting
>
> java -jar target/benchmarks.jar ".*AsyncAppenderLog4j2LocationBenchmark.*"
> -f 1 -wi 10 -i 20 -t 4 -si true
>
> No matching benchmarks. Miss
I am trying to run the location test and am getting
java -jar target/benchmarks.jar ".*AsyncAppenderLog4j2LocationBenchmark.*" -f 1
-wi 10 -i 20 -t 4 -si true
No matching benchmarks. Miss-spelled regexp?
Use EXTRA verbose mode to debug the pattern matching.
What’s up with that?
Ralph
Actually, tests should ONLY create files under the target directory - for
exactly this reason.
Ralph
> On May 4, 2016, at 10:49 AM, Gary Gregory wrote:
>
> When I run 'mvn clean test', I get this file left over:
>
> /log4j-parent/log4j-core/${filename}
>
> Is
When I run 'mvn clean test', I get this file left over:
/log4j-parent/log4j-core/${filename}
Is this expected instead of a real file name.
It should be cleaned up no matter what when the test is done...
Gary
--
E-Mail: [email protected] | [email protected]
Java Persis
You can use JUnit's Assume class for this type of thing.
-- Forwarded message --
From:
Date: 6 April 2016 at 13:47
Subject: logging-log4j2 git commit: LOG4J2-1295 bugfix: this test will only
pass if log4j is configured to be garbage-free. Skip this test in other
configura
Yes occasionally happens.
Not sure how this works.
Can try putting a sleep() call after removing the instrumentation to encourage
it to stop observing before shutdown.
Sent from my iPhone
> On 2016/04/05, at 3:29, Gary Gregory wrote:
>
> Has anyone seen this NPE before?
>
> Failed tests:
Has anyone seen this NPE before?
Failed tests:
GcFreeLoggingTest.testNoAllocationDuringSteadyStateLogging:60
expected:<[]> but was:<[Exception in thread "pool-1-thread-1"
java.lang.NullPointerException
at
com.google.monitoring.runtime.instrumentation.AllocationRecorder.getObjectSize(Allo
[
https://issues.apache.org/jira/browse/LOG4J2-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker closed LOG4J2-495.
--
> As a unit test developer, I want a JUnit rule to handle specific external
> configuration
Thanks, fixed now.
On Tue, Mar 8, 2016 at 10:13 PM, Remko Popma wrote:
>
>
> On Wed, Mar 9, 2016 at 3:35 AM, wrote:
>
>> Unit test for GelfLayout.encode
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
>> Commit:
>>
On Wed, Mar 9, 2016 at 3:35 AM, wrote:
> Unit test for GelfLayout.encode
>
>
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Commit:
> http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/58152b79
> Tree: http://git-wip-us.apache.org/repos/as
7;ve been building this just fine for a while
now.
> Can not build Log4j from git master due to a test failure in Log4j Core
> ---
>
> Key: LOG4J2-1247
> URL: https://issues.apache.org
ich
> cause the test to fail when rerunning the test
>
>
> Key: LOG4J2-1275
> URL: https://issues.apache.org/jira/
Sorry, the pull request that caused this had a follow-up that I just merged
in today.
On 3 March 2016 at 10:21, Ralph Goers wrote:
> This test is still failing.
>
> Ralph
>
> > On Mar 2, 2016, at 10:34 PM, Ralph Goers
> wrote:
> >
> > It appears that the newly
This test is still failing.
Ralph
> On Mar 2, 2016, at 10:34 PM, Ralph Goers wrote:
>
> It appears that the newly added testEventMapMessage is not working.
>
> Ralph
>
>> On Mar 2, 2016, at 8:08 PM, [email protected] wrote:
>>
>> Repository: logging
It appears that the newly added testEventMapMessage is not working.
Ralph
> On Mar 2, 2016, at 8:08 PM, [email protected] wrote:
>
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master 60d1ccd93 -> a57fc35b9
>
>
> LOG4J2-1227
>Test if the
, I can confirm that it also works for me as well on repeat
test runs. I've pushed it to master. Please verify and close.
> RollingAppenderNoUnconditionalDeleteTest leaves the rollingtest.log which
> cause the test to fail when rerunni
I recently merged a patch related to OSGi, but the unit tests for it will
only run after everything has been compiled at least once. Jenkins-wise, it
might be a good idea to split it up into a build and test cycle. Otherwise,
the OSGi tests are simply skipped every time.
--
Matt Sicker
-unconditional-deleteX directory
and its test subdirectory are removed when the test is created.
Doing it on creation 1. works for me (doing it in tearDown didn't), 2. ensure
that it is run even if the tests are abruptly halted.
Calling deleteDir() then deleteDirParent() does the 'recursion&#x
Ludovic HOCHET created LOG4J2-1275:
--
Summary: RollingAppenderNoUnconditionalDeleteTest leaves the
rollingtest.log which cause the test to fail when rerunning the test
Key: LOG4J2-1275
URL: https
Oh ok. :)
On 13 February 2016 at 21:47, Gary Gregory wrote:
> I made a silly mistake in the original version of the test. Fixed now.
> Thanks Matt!
>
> Gary
> On Feb 13, 2016 7:42 PM, "Matt Sicker" wrote:
>
>> Oh, and all the Loggers in log4j-api unit t
I made a silly mistake in the original version of the test. Fixed now.
Thanks Matt!
Gary
On Feb 13, 2016 7:42 PM, "Matt Sicker" wrote:
> Oh, and all the Loggers in log4j-api unit tests are TestLoggers unless you
> override that system property in the test class. So nothing new
Oh, and all the Loggers in log4j-api unit tests are TestLoggers unless you
override that system property in the test class. So nothing new to add
support for that.
On 13 February 2016 at 21:40, Matt Sicker wrote:
> It's set up as a custom log4j provider with a corresponding LoggerConte
It's set up as a custom log4j provider with a corresponding LoggerContext
and LoggerContextFactory. If you wanna use your own, you can override the
default via the system property log4j2.loggerContextFactory, though I'm not
sure that's what you're asking.
On 13 February 2016 at 17:54, Gary Gregory
Hi All:
Any hints on how to hook up a new logger to work like a TestLogger in:
org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2_ParameterizedMessageFactory()
?
Thank you,
Gary
--
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edi
[
https://issues.apache.org/jira/browse/LOG4J2-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1264.
-
Resolution: Invalid
This Jira project is for issues related to Log4j 2.
> ‘XSLTLayoutTest‘ t
Mahesh Waidande created LOG4J2-1264:
---
Summary: ‘XSLTLayoutTest‘ test case is failing on Ubuntu 15.04
(ppc64le) while building log4j-extras package
Key: LOG4J2-1264
URL: https://issues.apache.org/jira/browse
and then ran it in my Windows 7 VM with
both Maven 3.2.3 and 3.3.9 and did not get any errors. So it looks like there
must be something different about Anshu's environment.
> Can not build Log4j from git master due to a test failure i
tall" and it did download many jars
If I run it again it completes in about 13 minutes with same test failure
and three more
Results :
Failed tests:
RollingAppenderNoUnconditionalDeleteTest.testAppender:92 rolled over
lines expected:<17> but was:<18>
RollingAppenderNoUnconditio
long. Was this the first time you ran the
build and it downloaded a bunch of jars? The last time I ran 'mvn clean test'
it took about 13 minutes. What happens if you do it again? I wonder if this
could be a timing issue when your CPU get bogged down by other processes for
example.
> Ca
Anshu Garg created LOG4J2-1247:
--
Summary: Can not build Log4j from git master due to a test failure
in Log4j Core
Key: LOG4J2-1247
URL: https://issues.apache.org/jira/browse/LOG4J2-1247
Project: Log4j 2
YW ;-)
On Wed, Oct 21, 2015 at 4:05 PM, Remko Popma wrote:
> Thank you! I was sloppy.
>
> Sent from my iPhone
>
> > On 2015/10/22, at 5:12, [email protected] wrote:
> >
> > Repository: logging-log4j2
> > Updated Branches:
> > refs/heads/master 0eb6
Thank you! I was sloppy.
Sent from my iPhone
> On 2015/10/22, at 5:12, [email protected] wrote:
>
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master 0eb6ddfbf -> 3da6c31db
>
>
> Fix test to match code change.
>
> Project: http://git-wi
://garygregory.wordpress.com/2015/09/08/the-art-of-test-driven-development-per-test-logging/]
about how to use this feature.
> As a unit test developer, I want a JUnit rule to handle specific external
> configuration
Thank you sir!
Original message
From: Matt Sicker
Date: 10/14/2015 19:40 (GMT-08:00)
To: Log4J Developers List
Subject: Re: The Art of Test Driven Development: Per-Test Logging
That is such an awesome use of something that I thought was only useful for
writing Log4j
That is such an awesome use of something that I thought was only useful for
writing Log4j unit tests. I like it!
On 8 September 2015 at 21:22, Gary Gregory wrote:
> FYI:
>
>
> https://garygregory.wordpress.com/2015/09/08/the-art-of-test-driven-development-per-test-logging/
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1147.
Resolution: Fixed
Git master.
> Add %equalsIgnoreCase to PatternLayout to test and repl
Gary Gregory created LOG4J2-1147:
Summary: Add %equalsIgnoreCase to PatternLayout to test and
replace patterns with strings.
Key: LOG4J2-1147
URL: https://issues.apache.org/jira/browse/LOG4J2-1147
[
https://issues.apache.org/jira/browse/LOG4J2-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1145.
Resolution: Fixed
In Git master.
> Add %equals to PatternLayout to test and replace patterns w
Gary Gregory created LOG4J2-1145:
Summary: Add %equals to PatternLayout to test and replace patterns
with strings.
Key: LOG4J2-1145
URL: https://issues.apache.org/jira/browse/LOG4J2-1145
Project
FYI:
https://garygregory.wordpress.com/2015/09/08/the-art-of-test-driven-development-per-test-logging/
I just think this is just such a neat feature I wanted to share it.
Gary
--
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edition
<h
, 2015 at 4:50 PM, Remko Popma <mailto:[email protected]>> wrote:
> C'mon, we agreed on this!
>
> From our style guide:
> No wildcard imports in the main tree
>
> Wildcard imports, static or otherwise, are not used.
>
> <>Static wildcard imports i
c imports that are not *.
>
> Gary
>
>> On Tue, Sep 1, 2015 at 4:50 PM, Remko Popma wrote:
>> C'mon, we agreed on this!
>>
>> From our style guide:
>> No wildcard imports in the main tree
>>
>> Wildcard imports, static or otherwise, are no
ard imports*, static or otherwise, *are not used*.
> Static wildcard imports in the test tree
>
> *Wildcard static imports* are encouraged for test imports like JUnit,
> EasyMock, and Hamcrest.
>
> Sent from my iPhone
>
> On 2015/09/02, at 8:05, Gary Gregory wrote:
>
> Gros
C'mon, we agreed on this!
From our style guide:
No wildcard imports in the main tree
Wildcard imports, static or otherwise, are not used.
Static wildcard imports in the test tree
Wildcard static imports are encouraged for test imports like JUnit, EasyMock,
and Hamcrest.
Sent from my i
Gross. If you have more than one * you have no idea where stuff comes from.
Gary
On Tue, Sep 1, 2015 at 4:02 PM, Remko Popma wrote:
> The explicit static imports is not an improvement.
>
> I much prefer
> import static org.junit.Assert.*;
>
>
> Sent from my iPhone
>
> > On 2015/09/02, at 7:04,
The explicit static imports is not an improvement.
I much prefer
import static org.junit.Assert.*;
Sent from my iPhone
> On 2015/09/02, at 7:04, [email protected] wrote:
>
> import static org.junit.Assert.*;
-
To unsubscri
someone checking out the code would think and then do to
> modify the code.
>
> At the very minimum a URL to the Jira issue is required.
>
> Gary
> -- Forwarded message --
> From:
> Date: Thu, Aug 20, 2015 at 9:13 AM
> Subject: logging-log4j2 git commit: LO
: logging-log4j2 git commit: LOG4J2-1096 bugfix and additional unit
test for case where one or more arguments is null
To: [email protected]
Repository: logging-log4j2
Updated Branches:
refs/heads/master 8124d9b0d -> 31b7e7be5
LOG4J2-1096 bugfix and additional unit test for case where
ining: after running a test with -XX:+PrintCompilation
-XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining I found
"...ParameterizedMessage:
To: [email protected]
Repository: logging-log4j2
Updated Branches:
refs/heads/master ceb0a6208 -> 011f2c787
refactored Paramet
-- Forwarded message --
>> From:
>> Date: Sun, Aug 9, 2015 at 9:17 AM
>> Subject: [10/11] logging-log4j2 git commit: LOG4J2-599 small test
>> improvements
>> To: [email protected]
>>
>>
>> LOG4J2-599 small test improvements
>>
&g
:
> Date: Sun, Aug 9, 2015 at 9:17 AM
> Subject: [10/11] logging-log4j2 git commit: LOG4J2-599 small test
> improvements
> To: [email protected]
>
>
> LOG4J2-599 small test improvements
>
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Co
"@since log4j-2.4" should be "@since 2.4"
Gary
-- Forwarded message --
From:
Date: Sun, Aug 9, 2015 at 9:17 AM
Subject: [10/11] logging-log4j2 git commit: LOG4J2-599 small test
improvements
To: [email protected]
LOG4J2-599 small test improvements
Actually, the only tests I’ve seen fail were the ones in Jenkins. The last one
of those was on July 9. Those tests are
Test Result
<https://builds.apache.org/job/Log4j%202.x/1251/org.apache.logging.log4j$log4j-core/testReport/>
(3 failure
, Remko Popma wrote:
> Sometimes my WIFI internet connection at home stutters and I found that
> two of the SslConfigurationTest tests fail if my internet connection goes
> down.
>
> Not sure if that helps explain some of the spuriously failing test cases
> some of us oc
Sometimes my WIFI internet connection at home stutters and I found that two
of the SslConfigurationTest tests fail if my internet connection goes down.
Not sure if that helps explain some of the spuriously failing test cases
some of us occasionally see. Thought I should share
>>> call MarkerManager.clear() at the beginning and end of both LoggerTest and
>>> MarkerTest.
>>>
>>> Ralph
>>>
>>> > On Nov 30, 2014, at 10:57 PM, [email protected] wrote:
>>> >
>>> > Repository: logging-log4j
oth LoggerTest and
>> MarkerTest.
>>
>> Ralph
>>
>> > On Nov 30, 2014, at 10:57 PM, [email protected]
>> > <mailto:[email protected]> wrote:
>> >
>> > Repository: logging-log4j2
>> > Updated Branches:
>> > refs/hea
wrote:
>
>> I suppose that is one way to do it. Perhaps a better way would be to
>> call MarkerManager.clear() at the beginning and end of both LoggerTest and
>> MarkerTest.
>>
>> Ralph
>>
>> > On Nov 30, 2014, at 10:57 PM, [email protected] wrot
gt; On Nov 30, 2014, at 10:57 PM, [email protected]
> > <mailto:[email protected]> wrote:
> >
> > Repository: logging-log4j2
> > Updated Branches:
> > refs/heads/master ebb1c8066 -> d033a71eb
> >
> >
> > Test independence.
> >
> > Pro
[email protected] wrote:
> >
> > Repository: logging-log4j2
> > Updated Branches:
> > refs/heads/master ebb1c8066 -> d033a71eb
> >
> >
> > Test independence.
> >
> > Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
&g
fs/heads/master ebb1c8066 -> d033a71eb
>
>
> Test independence.
>
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/d033a71e
> Tree: http://git-wip-us.apache.org/repos/asf/logging-
> The simplest way to reproduce this from Maven is:
>
> mvn test
> -Dtest=org.apache.logging.log4j.jul.ApiLoggerTest,org.apache.logging.log4j.jul.CoreLoggerTest
>
> with:
>
> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
> 2014-08-11T16:58:10-04:00)
> Ma
The simplest way to reproduce this from Maven is:
mvn test
-Dtest=org.apache.logging.log4j.jul.ApiLoggerTest,org.apache.logging.log4j.jul.CoreLoggerTest
with:
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T16:58:10-04:00)
Maven home: C:\Java\apache-maven-3.2.3
Java
1 - 100 of 558 matches
Mail list logo
