https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1532 controller <p>CommitTransactionPayloadTest#testCandidateSerialization() as follows</p> <p>Running org.opendaylight.controller.cluster.datastore.persisted.CommitTransactionPayloadTest<br/> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.233 sec &lt;&lt;&lt; FAILURE! - in org.opendaylight.controller.cluster.datastore.persisted.CommitTransactionPayloadTest<br/> testCandidateSerialization(org.opendaylight.controller.cluster.datastore.persisted.CommitTransactionPayloadTest) Time elapsed: 0.129 sec &lt;&lt;&lt; FAILURE!<br/> java.lang.AssertionError: payload size expected:&lt;181&gt; but was:&lt;180&gt;<br/> at org.junit.Assert.fail(Assert.java:88)<br/> at org.junit.Assert.failNotEquals(Assert.java:743)<br/> at org.junit.Assert.assertEquals(Assert.java:118)<br/> at org.junit.Assert.assertEquals(Assert.java:555)<br/> at org.opendaylight.controller.cluster.datastore.persisted.CommitTransactionPayloadTest.testCandidateSerialization(CommitTransactionPayloadTest.java:116)</p> <p>Results :</p> <p>Failed tests: <br/> CommitTransactionPayloadTest.testCandidateSerialization:116 payload size expected:&lt;181&gt; but was:&lt;180&gt;</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1532

CommitTransactionPayloadTest#testCandidateSerialization() fails

Bug Resolved Done Isaku Yamahata Isaku Yamahata Tue, 12 Jul 2016 04:22:54 +0000 Fri, 15 Jul 2016 20:02:09 +0000 Fri, 15 Jul 2016 20:02:09 +0000 0.4.0 mdsal 0 0 <p><a href="https://git.opendaylight.org/gerrit/#/c/41691/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/41691/</a></p> <p>In order to reproduce it,<br/> Once compile controller and then run only the test as follows.<br/> mvn clean install<br/> then<br/> mvn -nsu '-Dtest=CommitTransactionPayloadTest#testCandidateSerialization' test -pl :sal-distributed-datastore</p> <p>The root cause is that historic transaction id and transaction id can vary depending on the running order. And the payload size may vary depending on its value due to WritableObject#writeLongs() and #writeLong().</p> <p>When the only test is run, historic id == 0 &amp;&amp; transaction id == 0.</p> Development External issue ID 6186 External issue URL Rank 0|i02r5j: