Re: [infinispan-dev] Hanging testsuite / bug in TestNG?
It doesn't know or care about it. But by disabling log4j console
appender you minimize the amount of text written to console and the risk
to trigger the surefire-report bug.
On 06/26/2012 06:51 PM, Sanne Grinovero wrote:
On 26 June 2012 16:38, Adrian Nistor <anistor(a)redhat.com>
wrote:
> Surefire-report plugin tries to capture the console output and holds it in a
> List of text lines and later it willattach the captured text to the test
> results report. The implementation is a bit clunky and if you have many
> threads logging to the console you'll most likely encounter that pesky
> ConcurrentModificationException. Disabling the console appender 'fixes' this
> :)
I trust you but didn't understand you. What console are you talking
about? I disabled the CONSOLE appender from lo4j, how can Surefire
know about the log4j configuration?
> I'm thinking on fixing this properly and submitting a patch to Maven.
That would be great!
> Adrian
>
>
> On 06/26/2012 05:41 PM, Sanne Grinovero wrote:
>> On 26 June 2012 08:53, Adrian Nistor <anistor(a)redhat.com> wrote:
>>> Have you tried to disable console logging and log only to a file? That
>>> 'cured' the ConcurrentModificationException for me.
>> Strange suggestions, but it works.. :D
>>
>> Now I have
>>
>> Failed tests:
>>
>>
testSTWithThirdWritingNonTxCache(org.infinispan.statetransfer.StateTransferFunctionalTest):
>> Entry under key [test100] was [null] but expected [100]
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
>