Hi, It is not Eclipse related, neither codec related. There were two issues
I had a wrong configuration of NumericConfig: new NumericConfig(4, NumberFormat.getNumberInstance(), NumericType.FLOAT)) I changed that to: new NumericConfig(4, NumberFormat.getNumberInstance(Locale.US), NumericType.FLOAT)) And the second problem was that I used the default "float" with precisionStep=0, however NumericRangeQuery requires precision step >=1 I tried all steps 1-8, and it worked only if the precison step of the field and of the NumericConfig are the same (for range queries) roman On Tue, Jan 8, 2013 at 7:34 PM, Roman Chyla <roman.ch...@gmail.com> wrote: > The test checks we are properly getting/indexing data - we index database > and fetch parts of the documents separately from mongodb. You can look at > the file here: > https://github.com/romanchyla/montysolr/blob/3c18312b325874bdecefceb9df63096b2cf20ca2/contrib/adsabs/src/test/org/apache/solr/update/TestAdsDataImport.java > > But your comment made me to run the tests on command line and I am seeing > I can't make it fail (it fails only inside Eclipse). Sorry, I should have > tried that myself, but I am so used to running unittests inside Eclipse it > didn't occur to me...i'll try to find out what is going on... > > thanks, > > roman > > > > > On Tue, Jan 8, 2013 at 6:53 PM, Chris Hostetter > <hossman_luc...@fucit.org>wrote: > >> >> : apparently, it fails also with @SuppressCodecs("Lucene3x") >> >> what exactly is the test failure message? >> >> When you run tests that use the lucene test framework, any failure should >> include information about the random seed used to run the test -- that >> random seed affects things like the codec used, the directoryfactory used, >> etc... >> >> Can you confirm wether the test reliably passes/fails consistently when >> you reuse the same seed? >> >> Can you elaborate more on what exactly your test does? ... we probably >> need to see the entire test to make sense of why you might get >> inconsistent failures. >> >> >> >> -Hoss >> > >
