Note that the native test runs have the know-flaky tests _enabled_ by default, run tests with
-Dtests.badapples=true to disable them. Second possibility is to look at the tests that failed and if there is an annotation @BadApple or @AwaitsFix ignore the failure if you can get the tests to pass when running individually. As Shawn says, this is a known issue that we're working on, but the technical debt is such that it'll be a long-term issue to fix. Best, Erick On Wed, Jul 11, 2018 at 7:13 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 7/10/2018 11:20 PM, tapan1707 wrote: >> >> We are trying to install solr-7.3.1 into our existing system (We have also >> made some changes by adding one custom query parser). >> >> I am having some build issues and it would be really helpful if someone >> can >> help. >> >> While running ant test(in the process of building the solr package), it >> terminates because of failed tests. > > > This is a known problem. Solr's tests are in not in a good state. > Sometimes they pass, sometimes they fail. Since there are so many tests and > a fair number of them do fail intermittently, this creates a situation where > on most test runs, there is at least one test failure. Run the tests enough > times, and eventually they will all pass ... but this usually takes many > runs. > > Looking at the commands you're using in your script: After a user has run > the "ant ivy-bootstrap" command once, ivy is downloaded into the user's home > directory and does not need to be downloaded again. Only the "ant package" > command (run in the "solr" subdirectory) is actually needed to build Solr. > The rest of the commands are not needed. > > As Emir said, you don't need to build Solr at all, even when using custom > plugins. You can download and use the binary package. > > There is effort underway to solve the problem with Solr tests. The initial > phase of that effort is to disable the tests that fail most frequently. The > second overlapping phase of the effort is to actually fix those tests so > that they don't fail - either by fixing bugs in the tests themselves, or by > fixing real bugs in Solr. > >> Also, does ant version has any effects in build?? > > > Ant 1.8 and 1.9 should work. Versions 1.10.0, 1.10.1, as well as 1.10.3 and > later should be fine, but 1.10.2 has a bug that results in the lucene-solr > build failing: > > https://issues.apache.org/jira/browse/LUCENE-8189 > >> At last, at present, we are using solr-6.4.2 which has zookeeper-3.4.6 >> dependency but for solr-7, the zookeeper dependency has been upgraded to >> 3.4.10, so my question is, At what extent does this might affect our >> system >> performance? Can we use zookeeper-3.4.6 with solr-7? >> (same with the jetty version) > > > You should be able to use any ZK 3.4.x server version with any version of > Solr. Most versions of Solr should also work with 3.5.x (still in beta) > servers. Early 4.x version s shipped with ZK 3.3.x, and the ZK project does > not guarantee compatibility between 3.3.x and 3.5.x. > > I can't guarantee that you won't run into bugs, but ZK is generally a very > stable piece of software. Each new release of ZK includes a very large list > of bugfixes. I have no idea what implications there are for performance. > You would need to ask a ZK support resource that question. The latest > stable release that is compatible with your software is the recommended > version. Currently that is 3.4.12. The 3.5.x releases are in beta. > > Thanks, > Shawn >
