Lastest git master does not build clean #3674
Comments
ghost
assigned 
|
Thanks a lot for taking the time to report the failures. This is great as we've been working on some rare failure cases the past few weeks. We see them since we switched to randomized testing [1]. We have seen something like the second one before, but not the first. Can you share the complete log output for both? I have a couple of questions: Were you running the tests while the machine was under load? |
|
on the second run, this first one worked. Started J0 PID([email protected]). [INFO] JVM J0: 0.76 .. 14.44 = 13.67s |
|
same for teh second. I will rerun all tests Started J0 PID([email protected]). [INFO] JVM J0: 0.79 .. 14.19 = 13.40s |
|
Thanks a lot for taking the time to do this! It is too bad the failure is not reproducible. We will keep investigating and keep you posted in case we find anything related to the failure. Sorry for not having more information at the moment. Please do not hesitate to paste any test failure logs here in the future, even if the logs are long. |
|
well i tried to build with mvn test -X for debug and it never endedd, the On Fri, Sep 13, 2013 at 9:24 AM, Britta Weber [email protected]:
James Michael DuPont |
|
could it be that this is similar to the line you are seeing: HEARTBEAT J1 PID([email protected]): 2013-09-13T19:06:48, stalled for 203s at: SearchWithRandomExceptionsTests.testRandomExceptions |
|
this is what it was full of, on smaller tests it produces only some of On Sat, Sep 14, 2013 at 4:56 AM, Britta Weber [email protected]:
James Michael DuPont |
|
SearchWithRandomExceptionsTests.testRandomExceptions has been fixed, see #3694 If that did not fix it, could you please provide the full log that contained the DEBUG line you pasted? |
|
I tried two times must 'mvn install' with no success with the error this thread is about. When I used only one JVM, it worked. Also, when I used the -X switch, and redirect the output to a text file, it works every time. So it's probably a timing issue. Using the -X switch probably slows it down enough to not have the timing issues. So, I have no debug script to offer. Just that I have the problem. I'll probably use the 1.0.0 jar at some point with it compiling to success with -X switch. |
|
@kwince if you just need to create a package and rather want to ignore the tests (dont get me wrong here, reporting test failures is perfectly valid and we are happy for that), you can run the packaging process without executing the tests via Also if you can reproduce test failures, dont bother to put in some information including the seeds, so we can reproduce it with our randomized test architecture. |
|
I would love to help with feedback. All I now about is 'mvn install/compile/package/deploy'. All the other switches I've never used, until friday, when I used the 'one VM' switch. Thank you for the skipTests switch. The problem I have compiling 1.0.0 can't be reproduced the way I'm running it, when I ask for a debug output. It slows down the build just enough that the error does not happen. It's got to be some knind of race condition. I can't provide any feedback under these circumstances, right? My original goal in compling ESearch was to find the 90.5 version and compile it. We are having the InetAddress Serializtion issue when we compile our project with Java 1.7, since your jars and zips are compiled with 1.6. We are having to downgrade our environments to 1.6 to get them running. I was hoping to test whether compiling Esearch with 1.7 would solve the problem (or find if the problem was in a dependency fo ESearch's). Never, ever approach a computer saying or even thinking "I will just do this quickly." From: Alexander Reelsen [email protected] @kwince if you just need to create a package and rather want to ignore the tests (dont get me wrong here, reporting test failures is perfectly valid and we are happy for that), you can run the packaging process without executing the tests via mvn -DskipTests=true package (you might know that already, just wanted to make sure you know in case you just want to play with the 1.0 snapshot zip/tar.gz archive). |
|
@kwince just as a reference That should generate the same packages than on elasticsearch.org - however it does not really matter, if you build with java6 or java7 compiler as we are setting the compiled target java version to 1.6 in the In the meantime we have continued our efforts to stabilize the tests further. If you run the tests yourself and you reliably manage to have a failing tests, please create a new github issue for this as well - which includes the mvn call to reproduce (we need a special call, which includes all the arguments needed to create the same setup for the randomized testing, this call is logged directly above the failed assertion of a failed test - or just include the full log). Thanks to everyone for helping and notifying! |
see elastic#3694 Also, this might have caused one of the problems described in issue elastic#3674
1> REPRODUCE WITH : mvn test -Dtests.seed=23CD52CEE15D72 -Dtests.class=org.elasticsearch.routing.SimpleRoutingTests -Dtests.method=testSimpleSearchRouting -Dtests.prefix=tests -Dtests.integration= -Dtests.nightly= -Dfile.encoding=UTF-8 -Duser.timezone=America/Los_Angeles
1> Throwable:
1> org.elasticsearch.index.mapper.MapperParsingException: External routing [0] and document path routing [null] mismatch
1> __randomizedtesting.SeedInfo.seed([23CD52CEE15D72:BC2675518BB49BEA]:0)
1> org.elasticsearch.index.mapper.internal.RoutingFieldMapper.validate(RoutingFieldMapper.java:185)
1> org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:520)
1> org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:452)
1> org.elasticsearch.index.shard.service.InternalIndexShard.prepareIndex(InternalIndexShard.java:358)
1> org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:201)
1> org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:544)
1> org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:429)
1> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
1> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
1> java.lang.Thread.run(Thread.java:724)
1>
1> [2013-09-11 16:12:37,660][INFO ][org.elasticsearch ] Test testSimpleSearchRouting(org.elasticsearch.routing.SimpleRoutingTests) finished
ERROR 0.18s | SimpleRoutingTests.testSimpleSearchRouting <<<
1> REPRODUCE WITH : mvn test -Dtests.seed=23CD52CEE15D72 -Dtests.class=org.elasticsearch.search.simple.SimpleSearchTests -Dtests.method=simpleDateMathTests -Dtests.prefix=tests -Dtests.integration= -Dtests.nightly= -Dfile.encoding=UTF-8 -Duser.timezone=America/Los_Angeles
1> Throwable:
1> java.lang.AssertionError: Hit count is 0 but 2 was expected. Total shards: 5 Successful shards: 5 & 0 shard failures:
1> __randomizedtesting.SeedInfo.seed([23CD52CEE15D72:16F64B1793B3F5AC]:0)
1> [...org.junit.]
1> org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertHitCount(ElasticsearchAssertions.java:103)
1> org.elasticsearch.search.simple.SimpleSearchTests.simpleDateMathTests(SimpleSearchTests.java:155)
1> [...sun., com.carrotsearch.randomizedtesting., java.lang.reflect.]
1> org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
1> org.apache.lucene.util.TestRuleFieldCacheSanity$1.evaluate(TestRuleFieldCacheSanity.java:51)
1> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
1> [...com.carrotsearch.randomizedtesting.]
1> org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
1> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:70)
1> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
1> [...com.carrotsearch.randomizedtesting.]
1> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
1> org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
1> [...com.carrotsearch.randomizedtesting.]
1> org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:43)
1> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
1> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:70)
1> org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
1> [...com.carrotsearch.randomizedtesting.]
1> java.lang.Thread.run(Thread.java:724)
1>
1> [2013-09-11 16:06:04,998][INFO ][org.elasticsearch ] Test simpleDateMathTests(org.elasticsearch.search.simple.SimpleSearchTests) finished
FAILURE 0.21s | SimpleSearchTests.simpleDateMathTests <<<
The text was updated successfully, but these errors were encountered: