<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 8, 2009, at 3:20 AM, Sanne Grinovero wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hello,<br>I'd appreciate some advice to understand if my tests are wrong, or if<br>my environment is screwed.<br><br>Having ported some of Łukasz's tests for the Lucene Directory, I have 6 tests:<br>one test fails and others appear to work, but in all logs I see this<br>kind of errors:<br><br>2009-10-08 00:55:37,493 ERROR [org.jgroups.protocols.UDP]<br>(Timer-1,bluestar.tana-50817) failed sending message to null (138<br>bytes)<br>java.lang.Exception: dest=/228.10.10.10:45588 (141 bytes)<br><span class="Apple-tab-span" style="white-space:pre"> </span>at org.jgroups.protocols.UDP._send(UDP.java:213)<br><br>when running "mvn clean test"<br><br>I get environment info:<br>~~~~~~~~~~~~~~~~~~~~~~~~~ ENVIRONMENT INFO ~~~~~~~~~~~~~~~~~~~~~~~~~~<br>bind.address = 127.0.0.1<br>java.runtime.version = 1.6.0_16-b01<br>java.runtime.name =Java(TM) SE Runtime Environment<br>java.vm.version = 14.2-b01<br>java.vm.vendor = Sun Microsystems Inc.<br>os.name = Linux<br>os.version = 2.6.30.8-64.fc11.x86_64<br>sun.arch.data.model = 64<br>sun.cpu.endian = little<br>protocol.stack = tcp<br>infinispan.marshaller.class = ${marshaller.class}<br>java.net.preferIPv4Stack = true<br>java.net.preferIPv6Stack = null<br>MAVEN_OPTS = null<br>~~~~~~~~~~~~~~~~~~~~~~~~~ ENVIRONMENT INFO ~~~~~~~~~~~~~~~~~~~~~~~~~~<br><br>So it appears the parent pom.xml is picked up correctly (as IPV4<br>preference and bind-address properties are defined there)<br><br>But if I run:<br>mvn clean test -Djava.net.preferIPv4Stack=true -Dbind.address=127.0.0.1<br><br>I get the same environment info but the tests behave differently: the<br>mentioned exceptions are not being logged any more,<br>but I get other kind of failures.<br>Also disabling the parallel execution of tests solves this, but<br>introduces other problems.<br><br>I can't understand the effect of setting these parameters on<br>infinispan/core, as many tests are failing already and have different<br>errors each time I relaunch the testsuite.<br>I really hate not being able to reproduce the errors, as they change<br>often, so it doesn't make much sense to post some stacktrace.<br>Is there any problem you might recognize in my environment?<br><br></div></blockquote><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font></div></blockquote>Once a test fails and doesn't cleanup resources /destroy caches other following tests run by same thread might end up with different clusters sizes (as nodes were not shutdown) and fail relatively random. If this is the problem, then the very first failing test should be the same, between test runs -> you can check that within the logs.</div><div><blockquote type="cite"><div>Are tests in trunk having some known problem?<br><br>thanks in advance,<br>Sanne<br><br>_______________________________________________<br>infinispan-dev mailing list<br><a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/infinispan-dev</div></blockquote></div><br></body></html>