Hudson build is back to normal : Lucene-Solr-tests-only-trunk #50

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Hudson build is back to normal : Solr-trunk #1281

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] Commented: (LUCENE-2702) BytesRefHash#get() should expect a BytesRef instances for consistency

[ https://issues.apache.org/jira/browse/LUCENE-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920892#action_12920892 ] Uwe Schindler commented on LUCENE-2702: --- +1, thanks for taking care!. As soon as thi

Is this warning expected?

Hi I ran SOLR tests today and I've noticed this print appearing several times: [junit] [junit] - Standard Error - [junit] 14.okt.2010 12:14:28 org.apache.solr.common.util.ConcurrentLRUCache finalize [junit] SEVERE: ConcurrentLRUCache was not destroyed p

[jira] Commented: (LUCENE-2702) BytesRefHash#get() should expect a BytesRef instances for consistency

[ https://issues.apache.org/jira/browse/LUCENE-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920895#action_12920895 ] Simon Willnauer commented on LUCENE-2702: - bq. Is BytesRefHash#get(int) currently

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch Thanks for the improvements, some comments and changes I did loc

Re: Is this warning expected?

On Thu, Oct 14, 2010 at 5:18 AM, Shai Erera wrote: > Hi > > I ran SOLR tests today and I've noticed this print appearing several times: > >     [junit] >     [junit] - Standard Error - >     [junit] 14.okt.2010 12:14:28 > org.apache.solr.common.util.ConcurrentLRUCache f

[jira] Updated: (LUCENE-2701) Factor maxMergeSize into findMergesForOptimize in LogMergePolicy

[ https://issues.apache.org/jira/browse/LUCENE-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated LUCENE-2701: --- Attachment: LUCENE-2701.patch Patch adds maxMergeMB handling to optimize as well. If there are no se

Re: Is this warning expected?

Thanks for the explanation Robert ! Shai On Thu, Oct 14, 2010 at 11:25 AM, Robert Muir wrote: > On Thu, Oct 14, 2010 at 5:18 AM, Shai Erera wrote: > > Hi > > > > I ran SOLR tests today and I've noticed this print appearing several > times: > > > > [junit] > > [junit] - Stan

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch Here a patch with the allocation problems resolved. Also the Di

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920909#action_12920909 ] Simon Willnauer commented on LUCENE-2690: - bq. The code in BooleanQueryRewrite use

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Willnauer updated LUCENE-2690: Attachment: LUCENE-2690.patch Updated patch after committing LUCENE-2707 I also fixed the

[jira] Commented: (SOLR-2002) improve build/tests

[ https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920916#action_12920916 ] Robert Muir commented on SOLR-2002: --- {quote} If I run a test individually, it does have al

[jira] Resolved: (LUCENE-2702) BytesRefHash#get() should expect a BytesRef instances for consistency

[ https://issues.apache.org/jira/browse/LUCENE-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Willnauer resolved LUCENE-2702. - Resolution: Fixed Fix Version/s: 4.0 committed in rev. 1022453 > BytesRefHash#ge

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch Merged patch. I had some addition asserts and some spelling prob

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690-attributes.patch This is the attributes hell patch (not yet finally do

[jira] Issue Comment Edited: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920930#action_12920930 ] Uwe Schindler edited comment on LUCENE-2690 at 10/14/10 7:52 AM: ---

Build failed in Hudson: Lucene-Solr-tests-only-3.x #54

See -- [...truncated 9720 lines...] [junit] [junit] 030*:*standard202.2two3xyz2010-10-14T12:16:07.504Z [junit] [junit] [junit] request was: start=0&q=*:*&qt=standar

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690-attributes.patch small improvements. Also added missing bottomChanged(

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920940#action_12920940 ] Robert Muir commented on LUCENE-2690: - I will play with the latest patch some, and hop

Hudson build is back to normal : Lucene-Solr-tests-only-3.x #55

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690-attributes.patch Here the patch for Robert, which fails the tie break

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2690: Attachment: LUCENE-2690.patch here is my patch, but the test still fails... I think it is a bug in

Build failed in Hudson: Lucene-Solr-tests-only-3.x #58

See -- [...truncated 9716 lines...] [junit] [junit] 040*:*standard202.2two3xyz2010-10-14T14:16:02.755Z [junit] [junit] [junit] request was: start=0&q=*:*&qt=standar

Re: Is this warning expected?

On Thu, Oct 14, 2010 at 5:18 AM, Shai Erera wrote: > I ran SOLR tests today and I've noticed this print appearing several times: > >     [junit] >     [junit] - Standard Error - >     [junit] 14.okt.2010 12:14:28 > org.apache.solr.common.util.ConcurrentLRUCache finalize

Build failed in Hudson: Lucene-Solr-tests-only-trunk #63

See -- [...truncated 2512 lines...] [junit] [junit] - Standard Output --- [junit] NOTE: reproduce with: ant test -Dtestcase=TestThreadSafe -Dtestmet

Re: Is this warning expected?

On Thu, Oct 14, 2010 at 10:24 AM, Yonik Seeley wrote: > I'll try and take another look after we get the test logging straitened out. > we can turn back on forking for each solr test to workaround it? I don't understand the logging and this would make tests much slower, but logging would work. -

Hudson build is back to normal : Lucene-Solr-tests-only-3.x #59

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Build failed in Hudson: Lucene-Solr-tests-only-trunk #64

See -- [...truncated 7836 lines...] [junit] [junit] Testsuite: org.apache.solr.common.util.DOMUtilTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.046 sec

[jira] Commented: (SOLR-2002) improve build/tests

[ https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920982#action_12920982 ] Yonik Seeley commented on SOLR-2002: I just tried peppering SolrTestCaseJ4 with checkLog

Hudson build is back to normal : Lucene-Solr-tests-only-trunk #65

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Build failed in Hudson: Lucene-Solr-tests-only-3.x #61

See -- [...truncated 9720 lines...] [junit] [junit] 040*:*standard202.2two3xyz2010-10-14T15:46:07.65Z [junit] [junit] [junit] request was: start=0&q=*:*&qt=standard

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch Here the final patch. There is only one special case: Our boolea

Hudson build is back to normal : Lucene-Solr-tests-only-3.x #62

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Is this warning expected?

On Thu, Oct 14, 2010 at 10:34 AM, Robert Muir wrote: > On Thu, Oct 14, 2010 at 10:24 AM, Yonik Seeley > wrote: > >> I'll try and take another look after we get the test logging straitened out. >> > > we can turn back on forking for each solr test to workaround it? I just tried that - doesn't see

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch This patch contains a better BooleanClause comparator that also

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921015#action_12921015 ] Simon Willnauer commented on LUCENE-2690: - Just as a first result here are the res

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921035#action_12921035 ] Uwe Schindler commented on LUCENE-2690: --- Simon: Just for comparing with Mike's resul

Build failed in Hudson: Lucene-Solr-tests-only-trunk #69

See -- [...truncated 7918 lines...] [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 1.038 sec [junit] [junit] Testsuite: org.apache.solr.schema.NotRequiredUniqu

Build failed in Hudson: Lucene-Solr-tests-only-3.x #65

See -- [...truncated 9720 lines...] [junit] [junit] 050*:*standard202.2two3xyz2010-10-14T17:51:28.248Z [junit] [junit] [junit] request was: start=0&q=*:*&qt=standar

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch Updated patch with optimization in ctor of FuzzyTermsEnum > Do

Speaking of tests

Anyone know how to print out, at the end of a long run of tests, the names of the actual tests that fail to the console? It's a pain to scroll through all the output to find the line and grepping through the reports is OK, but it would just be so much easier if it was summarized right there at

Hudson build is back to normal : Lucene-Solr-tests-only-trunk #70

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921057#action_12921057 ] Yonik Seeley commented on LUCENE-2690: -- Hmmm, it looks like this changes BQ.rewrite()

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch Revision of last patch (was buggy). About the "chicken and egg

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: (was: LUCENE-2690.patch) > Do MultiTermQuery boolean rewrites per segment > --

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921058#action_12921058 ] Uwe Schindler commented on LUCENE-2690: --- bq. Hmmm, it looks like this changes BQ.rew

Hudson build is back to normal : Lucene-Solr-tests-only-3.x #66

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Speaking of tests

The JUnit report task will generate a nice HTML version that illustrates with red what tests failed and you can easily drill into it. We have that wired into our build, right? Granted, it'd be nice to see a summary at the end of a JUnit run in the console, but I don't know of a way to make th

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921066#action_12921066 ] Yonik Seeley commented on LUCENE-2690: -- bq. This has a big speed degradion for lots o

Re: Speaking of tests

On Oct 14, 2010, at 2:18 PM, Erik Hatcher wrote: > The JUnit report task will generate a nice HTML version that illustrates with > red what tests failed and you can easily drill into it. We have that wired > into our build, right? Yeah, I can look at the reports, etc. > > Granted, it'd be

Build failed in Hudson: Lucene-Solr-tests-only-trunk #71

See Changes: [rmuir] fix solr logging in tests -- [...truncated 7964 lines...] [junit] Testsuite: org.apache.solr.handler.component.DistributedSpellCollatorTest [junit

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921077#action_12921077 ] Uwe Schindler commented on LUCENE-2690: --- Yes, Mr. No-inlining-Policeman :-) We are

Re: Speaking of tests

On Thu, Oct 14, 2010 at 2:28 PM, Grant Ingersoll wrote: > but, I just want a simple print out of the class names, as in: > > Tests failed: > FooTest.testFoo > BarTest.testBar > > Patches welcome, I suppose! > maybe open an issue? I think its possible we can improve this. ---

Hudson build is back to normal : Lucene-Solr-tests-only-trunk #72

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921081#action_12921081 ] Yonik Seeley commented on LUCENE-2690: -- bq. For random queries it had a huge positive

Build failed in Hudson: Lucene-Solr-tests-only-3.x #68

See -- [...truncated 10126 lines...] [junit] - --- [junit] Testsuite: org.apache.solr.handler.dataimport.TestEvaluatorBag [junit] Tests

Re: Speaking of tests

We could, at the least, make TEST org.apache.solr.analysis.TestTypeAsFieldFilterFactory FAILED stand out a bit more - prefix with a bunch of * or whatever. It would be nice if the red (in eclipse) error stream printed the TEST FAILED correctly, but I don't think that would be very easy to sy

Re: Speaking of tests

What we use to do is run 'ant test' with a redirection of standard output to a file. That way, the errors stand out - they appear in the console, and the rest of the test output goes to the file. Don't know if that's what you want, but it sure makes it much easier to spot the failing tests. Shai

Hudson build is back to normal : Lucene-Solr-tests-only-3.x #69

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch Attached is a new patch with two changes: - moved the BQ reorde

Build failed in Hudson: Lucene-Solr-tests-only-trunk #74

See -- [...truncated 7922 lines...] [junit] [junit] Testsuite: org.apache.solr.schema.TestBinaryField [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.319 sec

Build failed in Hudson: Lucene-Solr-tests-only-3.x #70

See -- [...truncated 8918 lines...] [junit] [junit] Testsuite: org.apache.solr.core.TestLegacyMergeSchedulerPolicyConfig [junit] Tests run: 1, Failures: 0, Errors: 0, Time ela

Build failed in Hudson: Lucene-Solr-tests-only-trunk #75

See -- [...truncated 7946 lines...] [junit] [junit] Testsuite: org.apache.solr.request.TestWriterPerf [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.57 sec

Hudson build is back to normal : Lucene-Solr-tests-only-3.x #71

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Build failed in Hudson: Lucene-Solr-tests-only-trunk #76

See -- [...truncated 9291 lines...] [junit] - --- [junit] Testsuite: org.apache.solr.handler.dataimport.TestEvaluatorBag [junit] Test

Hudson build is back to normal : Lucene-Solr-tests-only-trunk #77

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] Commented: (SOLR-792) Pivot (ie: Decision Tree) Faceting Component

[ https://issues.apache.org/jira/browse/SOLR-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921148#action_12921148 ] Ryan McKinley commented on SOLR-792: yonik -- I just added some simple docs... sorry for

[jira] Created: (LUCENE-2703) multitermquery scoring differences between 3x and trunk

multitermquery scoring differences between 3x and trunk --- Key: LUCENE-2703 URL: https://issues.apache.org/jira/browse/LUCENE-2703 Project: Lucene - Java Issue Type: Bug Affects Versio

[jira] Updated: (LUCENE-2703) multitermquery scoring differences between 3x and trunk

[ https://issues.apache.org/jira/browse/LUCENE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2703: Attachment: LUCENE-2703_test.patch > multitermquery scoring differences between 3x and trunk > ---

[jira] Commented: (LUCENE-2703) multitermquery scoring differences between 3x and trunk

[ https://issues.apache.org/jira/browse/LUCENE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921151#action_12921151 ] Robert Muir commented on LUCENE-2703: - The bug is in TermQuery(Term, int docfreq) if

Build failed in Hudson: Lucene-Solr-tests-only-trunk #79

See Changes: [uschindler] LUCENE-2671: remove last to warnings by a hack [yonik] tests: fix resource leaks + simplify -- [...truncated 8305 lines...] [junit] [junit]

Re: Speaking of tests

: Anyone know how to print out, at the end of a long run of tests, the : names of the actual tests that fail to the console? It's a pain to I typically use... grep -rL 'errors="0" failures="0"' test_output_dir (where test_output_dir depends on which set of tests failed) however two

[jira] Updated: (SOLR-1428) make ValueSourceParser and QParserPlugin implement SolrInfoMBean so people can use registry.jsp to see which ones are loaded

[ https://issues.apache.org/jira/browse/SOLR-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-1428: --- Attachment: SOLR-1428.patch I thought this would be really easy to bang in the airport last week, and this pa

Hudson build is back to normal : Lucene-Solr-tests-only-trunk #80

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] Updated: (LUCENE-2703) multitermquery scoring differences between 3x and trunk

[ https://issues.apache.org/jira/browse/LUCENE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2703: Attachment: LUCENE-2703_test.patch here's a patch, really a bad bug, the df was wrong here, but ne

[jira] Updated: (LUCENE-2703) multitermquery scoring differences between 3x and trunk

[ https://issues.apache.org/jira/browse/LUCENE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2703: Attachment: LUCENE-2703.patch > multitermquery scoring differences between 3x and trunk >

[jira] Updated: (LUCENE-2703) multitermquery scoring differences between 3x and trunk

[ https://issues.apache.org/jira/browse/LUCENE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2703: Attachment: (was: LUCENE-2703_test.patch) > multitermquery scoring differences between 3x and

[jira] Commented: (SOLR-1428) make ValueSourceParser and QParserPlugin implement SolrInfoMBean so people can use registry.jsp to see which ones are loaded

[ https://issues.apache.org/jira/browse/SOLR-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921158#action_12921158 ] Yonik Seeley commented on SOLR-1428: On a practical front, there are so many value sourc

[jira] Commented: (SOLR-2002) improve build/tests

[ https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921159#action_12921159 ] Hoss Man commented on SOLR-2002: Two things i've noticed recently that are kind of odd (and

[jira] Commented: (SOLR-1428) make ValueSourceParser and QParserPlugin implement SolrInfoMBean so people can use registry.jsp to see which ones are loaded

[ https://issues.apache.org/jira/browse/SOLR-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921166#action_12921166 ] Hoss Man commented on SOLR-1428: bq. On a practical front, there are so many value source pa

[jira] Commented: (LUCENE-2703) multitermquery scoring differences between 3x and trunk

[ https://issues.apache.org/jira/browse/LUCENE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921168#action_12921168 ] Robert Muir commented on LUCENE-2703: - i committed the bugfix, but i will write a good

[jira] Commented: (SOLR-2142) Faceting exception

[ https://issues.apache.org/jira/browse/SOLR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921169#action_12921169 ] Fuad Efendi commented on SOLR-2142: --- I have the same problem; recent trunk version, faceti

[jira] Updated: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2690: -- Attachment: LUCENE-2690.patch Patch with BytesRefHash parallel array sorting instead of sortin

[jira] Commented: (SOLR-2142) Faceting exception

[ https://issues.apache.org/jira/browse/SOLR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921181#action_12921181 ] Yonik Seeley commented on SOLR-2142: Any clues for reproducing this? I haven't been abl

[jira] Commented: (LUCENE-2690) Do MultiTermQuery boolean rewrites per segment

[ https://issues.apache.org/jira/browse/LUCENE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921182#action_12921182 ] Michael McCandless commented on LUCENE-2690: Test results on 10M Wiki index:

[jira] Commented: (SOLR-2142) Faceting exception

[ https://issues.apache.org/jira/browse/SOLR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921183#action_12921183 ] Fuad Efendi commented on SOLR-2142: --- Here is the failing test: import java.io.IOException

[jira] Issue Comment Edited: (SOLR-2142) Faceting exception

[ https://issues.apache.org/jira/browse/SOLR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921183#action_12921183 ] Fuad Efendi edited comment on SOLR-2142 at 10/14/10 8:07 PM: - He

[jira] Commented: (SOLR-2142) Faceting exception

[ https://issues.apache.org/jira/browse/SOLR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921187#action_12921187 ] Fuad Efendi commented on SOLR-2142: --- Related code: We probably need {code} if (b

Build failed in Hudson: Lucene-Solr-tests-only-3.x #77

See -- [...truncated 10133 lines...] [junit] - --- [junit] Testsuite: org.apache.solr.handler.dataimport.TestEvaluatorBag [junit] Tests

[jira] Created: (SOLR-2156) Solr Replication - SnapPuller fails to clean Old Index Directories on Full Copy

Solr Replication - SnapPuller fails to clean Old Index Directories on Full Copy --- Key: SOLR-2156 URL: https://issues.apache.org/jira/browse/SOLR-2156 Project: Solr

Re: Speaking of tests

In Junit4, there's a TestWatchman class that has a failed method that's called whenever a test fails. It *seems* like it would be possible to gather them all up and print them at the end, but I confess I have no clue how, and don't have time to look now. Not much help, but... Erick On Thu, Oct 1

Hudson build is back to normal : Lucene-Solr-tests-only-3.x #78

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] Commented: (SOLR-2142) Faceting exception

[ https://issues.apache.org/jira/browse/SOLR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921195#action_12921195 ] Fuad Efendi commented on SOLR-2142: --- Index contains terms with zero length. Probaly SOLR

[jira] Updated: (SOLR-2002) improve build/tests

[ https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-2002: --- Attachment: SOLR-2002.junit.xml.formatter.patch this patch gets the solr tests using the xml formatter by defa

[jira] Commented: (SOLR-2002) improve build/tests

[ https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921197#action_12921197 ] Yonik Seeley commented on SOLR-2002: The text format is so much easier to read, and it a

Re: Speaking of tests

: In Junit4, there's a TestWatchman class that has a failed method that's : called whenever a test fails. It *seems* like it would be possible to : gather them all up and print them at the end, but I confess I have no : clue how, and don't have time to look now. interesting... the intent of Test

[jira] Updated: (SOLR-2002) improve build/tests

[ https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2002: -- Attachment: SOLR-2002_buildfailed.patch heres a patch for a pet peeve of mine, if you run parallel tests

[jira] Commented: (SOLR-2002) improve build/tests

[ https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921199#action_12921199 ] Fuad Efendi commented on SOLR-2002: --- Words such as "xml formatter" sound extremely funny f

Build failed in Hudson: Lucene-Solr-tests-only-trunk #86

See -- [...truncated 7912 lines...] [junit] Testsuite: org.apache.solr.handler.component.QueryElevationComponentTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed:

  1   2   >