Thank-you for the tips. I still haven't had a single run pass out of around 20 attempts now on both the server and my desktop, but I'll just keep chipping away at it.
Ta, Greg On 29 April 2014 14:00, Tomás Fernández Löbbe <[email protected]> wrote: > Many times cloud-related/distrib tests fail due to timeouts, this could be > related to the overall load of your computer (probably generated by the > tests itself). I don’t know if this is the correct way, but I found it that > it’s much less probable for them to fail if I use less JVMs to run the > tests (by default my mac would use 4, but I set it to 2 if I see failures. > You can use the JVM parameter "tests.jvms" when running ant test) > > If you are working on some specific component you can filter which tests > to run in many ways, see “ant test-help”. It may be useful to use > tests.slow=false to skip the slow tests in most of your runs. > > "do I need to turn on a ZK server for integration testing?” > No, you don’t. Solr will start an embedded Zookeeper for the tests. > > "I've tried running those tests in isolation via IntelliJ and they all > report as passing” > Most probably is not related to this, but just in case: make sure when you > try to reproduce a failure on a test that you saw to use the same seed > (-Dtests.seed). The seed used should be in the output of the test where you > saw the failure. > > > [junit4] Tests with failures: > [junit4] - org.apache.solr.hadoop.MorphlineMapperTest (suite) > [junit4] > > Sorry, no idea about this one. > > > On Mon, Apr 28, 2014 at 7:47 PM, Greg Pendlebury < > [email protected]> wrote: > >> Heyo, >> >> I'm wondering if there is any additional doco and/or tricks to unit >> testing solr than this wiki page? http://wiki.apache.org/solr/TestingSolr >> >> Some details about my troubles are below if anyone cares to read, but I'm >> not so much looking for specific responses to why individual tests are >> failing. I'm more trying to work out whether I'm on the right track or >> missing some key information... like do I need to turn on a ZK server for >> integration testing? >> >> Or do I need to accept failed unit tests as a baseline before applying >> our patch? I don't typically like that, but this is an enormous test suite >> and I'd be happy just to get a pass up to the same level that 4.7.2 had >> prior to release. >> >> Ta, >> Greg >> >> >> Details >> ====== >> I downloaded the tagged 4.7.2 release Yesterday to apply a patch our team >> wants to test, but even before touching the codebase at all I cannot get >> the unit tests to pass. I'm struggling to even get consistent results. >> >> The most useful two end points I reach are: >> [junit4] Tests with failures: >> [junit4] - >> org.apache.solr.cloud.CustomCollectionTest.testDistribSearch >> [junit4] - >> org.apache.solr.cloud.DistribCursorPagingTest.testDistribSearch >> [junit4] - org.apache.solr.cloud.DistribCursorPagingTest (suite) >> [junit4] >> ... >> [junit4] Execution time total: 2 hours 6 minutes 50 seconds >> [junit4] Tests summary: 365 suites, 1570 tests, 1 suite-level error, 2 >> errors, 187 ignored (12 assumptions) >> >> And another one (don't have the terminal output on hand unfortunately) in >> the cloudera morphline suite. It is the same error as this though and fails >> after around an hour: >> http://mail-archives.apache.org/mod_mbox/flume-dev/201310.mbox/%3ccac6yyrj2cv89hntdeel7t0qlq8zjbwjynbtcveucxlzdmyv...@mail.gmail.com%3E >> >> I've tried running those tests in isolation via IntelliJ and they all >> report as passing... the logs show exceptions about ZK session expiry for >> some (not all) but I assume those are trapped expected exceptions since >> JUnit is passing them? >> >> Given the response in the message I linked just above re: windows support >> I tried shifting the build up to a RHEL6 server this morning but I've tried >> two runs now and both failed with this odd error: >> [junit4] Tests with failures: >> [junit4] - org.apache.solr.hadoop.MorphlineMapperTest (suite) >> [junit4] >> ... >> [junit4] Execution time total: 42 seconds >> [junit4] Tests summary: 7 suites, 35 tests, 2 suite-level errors, 5 >> ignored >> >> I only say odd because they run for half an hour and then report 42 >> seconds. >> >> Thanks again if you've read all this. >> > >
