[infinispan-issues] [JBoss JIRA] (ISPN-2658) org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744856#comment-12744856 ] 

RH Bugzilla Integration commented on ISPN-2658:
-----------------------------------------------

Tristan Tarrant <ttarrant at redhat.com> changed the Status of [bug 888693|https://bugzilla.redhat.com/show_bug.cgi?id=888693] from MODIFIED to ON_QA
                
> org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey  fails constantly on all environments
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-2658
>                 URL: https://issues.jboss.org/browse/ISPN-2658
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.2.0.Beta6
>            Reporter: Anna Manukyan
>            Assignee: Galder Zamarreño
>              Labels: testsuite_stability
>             Fix For: 5.2.0.CR1
>
>         Attachments: testModificationsOnSameCustomKey-2.log
>
>
> org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey  test fails on all environments (RHEL, Windows, Solaris - JDK7, Open JDK7, IBM JDK7). 
> The error message is:
> {code}
> Error Message
> Serialization count: expected 4 but was 5
> Stacktrace
> java.lang.AssertionError: Serialization count: expected 4 but was 5
> 	at org.infinispan.marshall.MarshalledValueTest.assertSerializationCounts(MarshalledValueTest.java:135)
> 	at org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey(MarshalledValueTest.java:452)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:601)
> 	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> 	at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
> 	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> 	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> 	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> 	at org.testng.TestRunner.privateRun(TestRunner.java:767)
> 	at org.testng.TestRunner.run(TestRunner.java:617)
> 	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> 	at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> 	at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> 	at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> 	at java.lang.Thread.run(Thread.java:722)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira