Low pause GC for java 1.6

We are getting large Solr pauses on Java garbage collection in 1.6 Java. We have tried CMS. But we still have. 4 second wait on GC. What works well for Solr when using 16 GB of RAM? I have read lots of articles and now just looking for practical advise and examples. Sent from my Mobile device

[jira] [Updated] (SOLR-1725) Script based UpdateRequestProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-1725: --- Attachment: SOLR-1725.patch Updated patch, changes... * refactor TestBadConfig and BadIndexSchemaTest to use

[jira] [Comment Edited] (LUCENE-4062) More fine-grained control over the packed integer implementation that is chosen

[ https://issues.apache.org/jira/browse/LUCENE-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404234#comment-13404234 ] Toke Eskildsen edited comment on LUCENE-4062 at 6/29/12 10:03 PM: -

Re: Use of @Slow annotation on tests

bq. Perhaps an ant target "quicktest" or something instead of the -D? You can set this permanently in your defaults (or set a shell alias with -D? :) I'd rather not have yet another ant target if not really needed... Dawid

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 14800 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14800/ 1 tests failed. REGRESSION: org.apache.lucene.analysis.core.TestRandomChains.testRandomChains Error Message: startOffset must be non-negative, and endOffset must be >= startOffset, startOffset=3,endOffset=2 Stack Trace: j

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #14: POMs out of sync

I'll @Ignore it until I figure out what's happening. On Fri, Jun 29, 2012 at 11:13 PM, Dawid Weiss wrote: > This is odd, really. I'll take a look but not today. > > Dawid > > On Fri, Jun 29, 2012 at 5:44 PM, Steven A Rowe wrote: >> Hmm, this is likely a Maven Surefire-only problem. >> >> I'm clu

RE: question about maven artifacts publishing instructions

Calling 'ant stage-maven-artifacts' with sysprop maven.dist.dir set to a parent directory containing both Lucene and Solr artifacts should be no problem. 'ant stage-maven-artifacts' invokes dev-tools/scripts/write.stage.maven.build.xml.pl, which works by: a) recursing over the directory pointed

[jira] [Commented] (LUCENE-4062) More fine-grained control over the packed integer implementation that is chosen

[ https://issues.apache.org/jira/browse/LUCENE-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404234#comment-13404234 ] Toke Eskildsen commented on LUCENE-4062: +1 for replacing the Packed64SingleBlock

[JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 318 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/318/ 1 tests failed. REGRESSION: org.apache.solr.handler.dataimport.TestSqlEntityProcessorDelta2.testCompositePk_DeltaImport_add_delete Error Message: Exception during query Stack Trace: java.lang.RuntimeException: E

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #14: POMs out of sync

This is odd, really. I'll take a look but not today. Dawid On Fri, Jun 29, 2012 at 5:44 PM, Steven A Rowe wrote: > Hmm, this is likely a Maven Surefire-only problem. > > I'm clueless about the interaction between Surefire your randomized runner, > Dawid - should this test be ignored under Suref

[jira] [Updated] (SOLR-3584) Spellcheck shouldn't throw NPE on config errors

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer updated SOLR-3584: - Summary: Spellcheck shouldn't throw NPE on config errors (was: Solr shouldn't throw NPE on config errors)

[jira] [Reopened] (SOLR-3584) Solr shouldn't throw NPE on config errors

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer reopened SOLR-3584: -- Re-open with a clarified title > Solr shouldn't throw NPE on config errors > --

[jira] [Updated] (SOLR-3584) Solr shouldn't throw NPE on config errors

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer updated SOLR-3584: - Summary: Solr shouldn't throw NPE on config errors (was: Solr shouldn't throw NPE when spellcheck diction

[jira] [Commented] (SOLR-3584) Solr shouldn't throw NPE when spellcheck dictionary isn'

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404144#comment-13404144 ] Andy Lester commented on SOLR-3584: --- It seems that the cause is in the section. I had

Re: Query, Searcher, Weight, Similarity = ?

On 06/29/2012 02:55 PM, Mike Sokolov wrote: On 06/29/2012 02:17 PM, Robert Muir wrote: On Fri, Jun 29, 2012 at 2:12 PM, Mike Sokolov wrote: This has been elucidating, thanks! On a related topic: I need the ability to pull results lazily, so that I can decide whether to terminate the sear

[jira] [Updated] (SOLR-3584) Solr shouldn't throw NPE when spellcheck dictionary isn'

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer updated SOLR-3584: - Priority: Minor (was: Major) Summary: Solr shouldn't throw NPE when spellcheck dictionary isn' (was:

[jira] [Commented] (SOLR-3584) NPE when trying to spellcheck.build

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404142#comment-13404142 ] Andy Lester commented on SOLR-3584: --- I was doing as instructed by Chris Hostetter (hoss)

[jira] [Resolved] (SOLR-3584) NPE when trying to spellcheck.build

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer resolved SOLR-3584. -- Resolution: Invalid Andy, Please use the user's mailing list for questions like this. I think you just

[jira] [Commented] (SOLR-3584) NPE when trying to spellcheck.build

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404125#comment-13404125 ] Andy Lester commented on SOLR-3584: --- My Tomcat catalina.out log file doesn't have anythin

[jira] [Comment Edited] (SOLR-3584) NPE when trying to spellcheck.build

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404119#comment-13404119 ] Andy Lester edited comment on SOLR-3584 at 6/29/12 6:58 PM: Rel

[jira] [Commented] (SOLR-3584) NPE when trying to spellcheck.build

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404119#comment-13404119 ] Andy Lester commented on SOLR-3584: --- Relevant config from my solrconfig.xml

[jira] [Comment Edited] (SOLR-3584) NPE when trying to spellcheck.build

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404119#comment-13404119 ] Andy Lester edited comment on SOLR-3584 at 6/29/12 6:57 PM: Rel

Re: Query, Searcher, Weight, Similarity = ?

On 06/29/2012 02:17 PM, Robert Muir wrote: On Fri, Jun 29, 2012 at 2:12 PM, Mike Sokolov wrote: This has been elucidating, thanks! On a related topic: I need the ability to pull results lazily, so that I can decide whether to terminate the search iteration early, and ultimately I need to

[jira] [Commented] (SOLR-3584) NPE when trying to spellcheck.build

[ https://issues.apache.org/jira/browse/SOLR-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404117#comment-13404117 ] Andy Lester commented on SOLR-3584: --- Full NPE: HTTP Status 500 - null java.lang.NullPoin

[jira] [Created] (SOLR-3584) NPE when trying to spellcheck.build

Andy Lester created SOLR-3584: - Summary: NPE when trying to spellcheck.build Key: SOLR-3584 URL: https://issues.apache.org/jira/browse/SOLR-3584 Project: Solr Issue Type: Bug Components

unit test for search components that works only for distributed search

I have written a custom search component, but the code only supports distributed search. Since we dont use non-distributed search and solr's search flow works differently for non-distributed case, we decided to support only on distributed search. I am trying to write unit test for my custom comp

Re: Query, Searcher, Weight, Similarity = ?

On Fri, Jun 29, 2012 at 2:12 PM, Mike Sokolov wrote: > This has been elucidating, thanks! > > On a related topic: > > I need the ability to pull results lazily, so that I can decide whether to > terminate the search iteration early, and ultimately I need to delegate that > decision to callers of *

Re: IRC chat tonight on lucene spatial?

I meant 3:30am UTC Monday, not Sunday. The UTC/ET thing confused me. On Jun 29, 2012, at 2:03 PM, Smiley, David W. wrote: > That was a bust :-( > > Instead, I propose 3:30am UTC (same time) Sunday night. I'll use UTC times > because it is more universal for us as we span the globe. > > ~ Dav

Re: Query, Searcher, Weight, Similarity = ?

This has been elucidating, thanks! On a related topic: I need the ability to pull results lazily, so that I can decide whether to terminate the search iteration early, and ultimately I need to delegate that decision to callers of *my* API. My first question is: did I overlook support for thi

Re: IRC chat tonight on lucene spatial?

That was a bust :-( Instead, I propose 3:30am UTC (same time) Sunday night. I'll use UTC times because it is more universal for us as we span the globe. ~ David On Jun 28, 2012, at 4:24 PM, Smiley, David W. wrote: > Chris, Ryan, > I propose, if possible, that we chat on irc at #lucene-d

Re: Use of @Slow annotation on tests

+1 Love it On Jun 29, 2012, at 4:42 AM, Dawid Weiss wrote: > Hi. I would like to change the use of @Slow. Currently only this test: > > Test2BTerms#test2BTerms > > is annotated with this annotation. I don't know how slow it really is, > but I would like to: > > * change this particular test to

Re: version checkout

: So I guess there is no way of me doing a patch for 3.6.0 since the issue in : JIRA I reported is not a : bug (but a new feature). Ok. Than, I'll do a patch for the 4.0 As a general rule, features should always be developed against trunk, and th

Re: Query, Searcher, Weight, Similarity = ?

On Fri, Jun 29, 2012 at 9:02 AM, Arjun Dhar wrote: > Hi, > I'm new and that is my disclaimer to the stupid question I am about to ask. > > Am trying to form a conceptual picture of the relation between Query <--> > Weight <--> IndexReader, Scorer, Searcher <--> Similarity > > *From what I gather :

Query, Searcher, Weight, Similarity = ?

Hi, I'm new and that is my disclaimer to the stupid question I am about to ask. Am trying to form a conceptual picture of the relation between Query <--> Weight <--> IndexReader, Scorer, Searcher <--> Similarity *From what I gather : (and someone please validate or correct me) * 1. We want *Queri

Re: [JENKINS] Lucene-Solr-trunk-Linux-Java7-64 - Build # 438 - Failure!

I added the missing ASL header. On Thu, Jun 28, 2012 at 4:54 PM, Policeman Jenkins Server < jenk...@sd-datasolutions.de> wrote: > Build: > http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java7-64/438/ > > All tests passed > > Build Log: > [...truncated 15182 lines...] > BUILD FAILE

RE: question about maven artifacts publishing instructions

I think it's fine, but later today I'll take a look at the stage-maven-artifacts ant target implementation to make sure. - Steve -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Friday, June 29, 2012 1:01 PM To: dev@lucene.apache.org Subject: Re: question about maven

Re: question about maven artifacts publishing instructions

On Fri, Jun 29, 2012 at 12:57 PM, Steven A Rowe wrote: > Was it a parent directory of both the Lucene and the Solr artifacts? > yes. is this a problem? -- lucidimagination.com - To unsubscribe, e-mail: dev-unsubscr...@lucene.a

RE: question about maven artifacts publishing instructions

Hmm, interesting. When I wrote those instructions in the process of performing them for the last release, the Lucene invocation only staged the Lucene artifacts, likewise for the Solr invocation and artifacts. Where did the artifacts come from? Did you use the download script referred to in t

[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #533: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/533/ 1 tests failed. FAILED: org.apache.lucene.util.TestMaxFailuresRule.testMaxFailures Error Message: expected:<100> but was:<1> Stack Trace: java.lang.AssertionError: expected:<100> but was:<1> at org.junit.Assert.fail(Asser

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #14: POMs out of sync

Hmm, this is likely a Maven Surefire-only problem. I'm clueless about the interaction between Surefire your randomized runner, Dawid - should this test be ignored under Surefire? Under other test runners too, maybe? (IntelliJ, Eclipse) Steve -Original Message- From: Steven A Rowe [ma

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #14: POMs out of sync

Dawid, You checked in changes to this test (TestMaxFailuresRule.java) at revision 1355279. This Jenkins Maven build's checked out svn revision is 1355359. So it looks like there might be a problem with your commit? Steve -Original Message- From: Apache Jenkins Server [mailto:jenk...@

[jira] [Commented] (LUCENE-4062) More fine-grained control over the packed integer implementation that is chosen

[ https://issues.apache.org/jira/browse/LUCENE-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403971#comment-13403971 ] Adrien Grand commented on LUCENE-4062: -- This is very interesting! Results computed

[JENKINS-MAVEN] Lucene-Solr-Maven-4.x #14: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/14/ 1 tests failed. FAILED: org.apache.lucene.util.TestMaxFailuresRule.testMaxFailures Error Message: expected:<100> but was:<1> Stack Trace: java.lang.AssertionError: expected:<100> but was:<1> at org.junit.Assert.fail(Assert.j

[jira] [Updated] (LUCENE-4062) More fine-grained control over the packed integer implementation that is chosen

[ https://issues.apache.org/jira/browse/LUCENE-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toke Eskildsen updated LUCENE-4062: --- Attachment: PackedIntsBenchmark.java Packed64Strategy.java Nice trick with t

[jira] [Commented] (LUCENE-4161) Make PackedInts usable by codecs

[ https://issues.apache.org/jira/browse/LUCENE-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403910#comment-13403910 ] Adrien Grand commented on LUCENE-4161: -- bq. Can we find a better name for computeN?

[JENKINS] Solr-trunk - Build # 1899 - Still Failing

Build: https://builds.apache.org/job/Solr-trunk/1899/ 1 tests failed. FAILED: org.apache.solr.cloud.RecoveryZkTest.testDistribSearch Error Message: Thread threw an uncaught exception, thread: Thread[Lucene Merge Thread #2,6,] Stack Trace: java.lang.RuntimeException: Thread threw an uncaught exc

[jira] [Closed] (LUCENE-4171) Performance improvements to Packed64

[ https://issues.apache.org/jira/browse/LUCENE-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand closed LUCENE-4171. Resolution: Fixed Fix Version/s: 4.0 Assignee: Adrien Grand Lucene Fields: Patc

Re: svn commit: r1355346 - in /lucene/dev/trunk/lucene: CHANGES.txt core/src/java/org/apache/lucene/util/packed/Packed64.java

On Fri, Jun 29, 2012 at 2:55 PM, Robert Muir wrote: > Can we move this CHANGES entry under the beta section? Fixed. Thanks, Robert. -- Adrien - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands,

question about maven artifacts publishing instructions

Currently we have: http://wiki.apache.org/lucene-java/PublishMavenArtifacts http://wiki.apache.org/solr/PublishMavenArtifacts But it seems to me if you follow the lucene instructions, that it does lucene+solr in one shot. So I think we can nuke one of these pages and just add a note that it does

Re: maven artifacts review

Thanks for reviewing Sami. I'll wait a bit more before deploying these just to be sure. Realistically I put the non-maven artifacts out very late last night, and there is the website stuff too, so I'm targeting monday for flipping the switch on the website/sending emails out, so there is no rush.

Re: svn commit: r1355346 - in /lucene/dev/trunk/lucene: CHANGES.txt core/src/java/org/apache/lucene/util/packed/Packed64.java

Can we move this CHANGES entry under the beta section? On Fri, Jun 29, 2012 at 8:52 AM, wrote: > Author: jpountz > Date: Fri Jun 29 12:52:54 2012 > New Revision: 1355346 > > URL: http://svn.apache.org/viewvc?rev=1355346&view=rev > Log: > LUCENE-4171: Performance improvements to Packed64 (Toke Es

Re: Use of @Slow annotation on tests

+1 Perhaps an ant target "quicktest" or something instead of the -D? I don't have any strong feelings which would be better so whatever the people doing the work think. But running "ant test" on my 2009-vintage laptop has been painful lately On Fri, Jun 29, 2012 at 6:54 AM, Robert Muir wrote: >

Re: maven artifacts review

I smoke tested the solrj artifact with a dead simple app, seems to work. -- Sami Siren On Fri, Jun 29, 2012 at 2:55 PM, Robert Muir wrote: > Hello. I think I created a staging instance of 4.0.0-ALPHA (lucene and solr). > > Could someone eyeball it before I push it out there?: > https://reposito

[JENKINS] Lucene-Solr-4.x-Windows-Java6-64 - Build # 190 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/190/ 1 tests failed. REGRESSION: org.apache.solr.spelling.suggest.SuggesterWFSTTest.testSuggestions Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Exception during query at _

[jira] [Updated] (LUCENE-4080) SegmentReader.numDeletedDocs() sometimes gives an incorrect numDeletedDocs

[ https://issues.apache.org/jira/browse/LUCENE-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-4080: - Attachment: LUCENE-4080.patch New patch (simpler than the previous ones). This time, I only remo

maven artifacts review

Hello. I think I created a staging instance of 4.0.0-ALPHA (lucene and solr). Could someone eyeball it before I push it out there?: https://repository.apache.org/content/repositories/orgapachelucene-286/ Thanks -- lucidimagination.com ---

Re: [JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 1090 - Failure!

OK I opened LUCENE-4182. Mike McCandless http://blog.mikemccandless.com On Fri, Jun 29, 2012 at 6:03 AM, Dawid Weiss wrote: > I don't think there's a jira entry for this, but I also saw it on my > build server (ram was X expected Y). Don't know what to call it though > (what this assertion actu

[jira] [Created] (LUCENE-4182) DocumentsWriterFlushControl.assertMemory tripped by NGramTokenizerTest.testRandomStrings

Michael McCandless created LUCENE-4182: -- Summary: DocumentsWriterFlushControl.assertMemory tripped by NGramTokenizerTest.testRandomStrings Key: LUCENE-4182 URL: https://issues.apache.org/jira/browse/LUCENE-41

[jira] [Commented] (LUCENE-4161) Make PackedInts usable by codecs

[ https://issues.apache.org/jira/browse/LUCENE-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403843#comment-13403843 ] Michael McCandless commented on LUCENE-4161: Wow, this patch is impressive!

[jira] [Commented] (SOLR-1725) Script based UpdateRequestProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403841#comment-13403841 ] Robert Muir commented on SOLR-1725: --- We do have sugar for this already actually: IOUtils

[jira] [Commented] (SOLR-1725) Script based UpdateRequestProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403838#comment-13403838 ] Robert Muir commented on SOLR-1725: --- {quote} fixed InputStreamReader to use UTF-8 {quote}

[jira] [Resolved] (LUCENE-4178) FieldType.setTokenized shoudl be true by default

[ https://issues.apache.org/jira/browse/LUCENE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-4178. - Resolution: Fixed Fix Version/s: 5.0 4.0 > FieldType.setTokenized

Re: How to start apache solr automatically in linux server for drupal 7

Hi, Install the "daemon" Linux package. This one allows to correctly fork processes into background. It also creates PID files and set the user account on starting. After that you only need a upstart (e.g. used on ubuntu) or init.d script to start it on boot. Alternatively add it as @reboot cro

Re: Use of @Slow annotation on tests

On Fri, Jun 29, 2012 at 6:50 AM, Dawid Weiss wrote: > Yep, sure. All these test groups can be triggered via system > properties so sure -- a weekly build could enable the @Weekly group > and run a full test. I don't know how heavy it is on the filesystem > though (and if Jenkins can handle this pa

[jira] [Assigned] (LUCENE-4094) Randomize file.encoding

[ https://issues.apache.org/jira/browse/LUCENE-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss reassigned LUCENE-4094: --- Assignee: Dawid Weiss > Randomize file.encoding > --- > >

How to start apache solr automatically in linux server for drupal 7

Hello all, I am a newbie to drupal. I am working on drupal commerce for an ecommerce site.Here i need to implement apache solr search for autocomplete of product search . For this function , am running "java -jar start.jar" comand in apache-solr directory. I need this to be automatic

Re: Use of @Slow annotation on tests

Yep, sure. All these test groups can be triggered via system properties so sure -- a weekly build could enable the @Weekly group and run a full test. I don't know how heavy it is on the filesystem though (and if Jenkins can handle this particular test). Dawid On Fri, Jun 29, 2012 at 12:46 PM, Rob

[jira] [Resolved] (LUCENE-4181) Change the semantics of @Slow on tests

[ https://issues.apache.org/jira/browse/LUCENE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss resolved LUCENE-4181. - Resolution: Fixed I'll commit it in since there was just one test marked as @Slow and it doesn't

[jira] [Commented] (LUCENE-4181) Change the semantics of @Slow on tests

[ https://issues.apache.org/jira/browse/LUCENE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403826#comment-13403826 ] Dawid Weiss commented on LUCENE-4181: - Before (full tests, solr and lucene): {noforma

Re: Use of @Slow annotation on tests

On Fri, Jun 29, 2012 at 6:31 AM, Dawid Weiss wrote: >>> is annotated with this annotation. I don't know how slow it really is, >> >> couple of hours :) > > We need @SuperSlow. Or @YouWillTurnToDustBeforeItCompletes. > >> +1! Of course from time to time we should try to fix these slow tests > > Yep

Re: Use of @Slow annotation on tests

>> is annotated with this annotation. I don't know how slow it really is, > > couple of hours :) We need @SuperSlow. Or @YouWillTurnToDustBeforeItCompletes. > +1! Of course from time to time we should try to fix these slow tests Yep, it is unavoidable that the time will be increasing but we have

[jira] [Updated] (LUCENE-4181) Change the semantics of @Slow on tests

[ https://issues.apache.org/jira/browse/LUCENE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss updated LUCENE-4181: Attachment: LUCENE-4181.patch Applied @Slow on the slowest tests. > Change the se

[JENKINS] Lucene-4.x - Build # 23 - Still Failing

Build: https://builds.apache.org/job/Lucene-4.x/23/ All tests passed Build Log: [...truncated 28881 lines...] [...truncated 28765 lines...] rat-sources: [echo] [echo] * [echo] Summary [echo] --- [echo] Generated at

Re: Use of @Slow annotation on tests

On Fri, Jun 29, 2012 at 4:42 AM, Dawid Weiss wrote: > Hi. I would like to change the use of @Slow. Currently only this test: > > Test2BTerms#test2BTerms > > is annotated with this annotation. I don't know how slow it really is, couple of hours :) > My motivation is that I would like to be able t

[jira] [Resolved] (LUCENE-3832) Port BasicAutomata.stringUnion from Brics to Lucene

[ https://issues.apache.org/jira/browse/LUCENE-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss resolved LUCENE-3832. - Resolution: Fixed > Port BasicAutomata.stringUnion from Brics to Lucene > --

Re: [JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 1090 - Failure!

I don't think there's a jira entry for this, but I also saw it on my build server (ram was X expected Y). Don't know what to call it though (what this assertion actually does). Dawid On Fri, Jun 29, 2012 at 11:59 AM, Michael McCandless wrote: > This is the root cause: > >     [junit4]    > Cause

Re: [JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 1090 - Failure!

This is the root cause: [junit4]> Caused by: java.lang.AssertionError: ram was 41605728 expected: 40986328 flush mem: 27371536 activeMem: 14234192 pendingMem: 0 flushingMem: 2 blockedMem: 0 peakDeltaMem: 3715948 [junit4]>at __randomizedtesting.SeedInfo.seed([256D0DE54BD0473A

[jira] [Commented] (LUCENE-4172) clean up redundant throws clauses

[ https://issues.apache.org/jira/browse/LUCENE-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403806#comment-13403806 ] Michael McCandless commented on LUCENE-4172: I prefer the individual imports,

[jira] [Commented] (LUCENE-3832) Port BasicAutomata.stringUnion from Brics to Lucene

[ https://issues.apache.org/jira/browse/LUCENE-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403805#comment-13403805 ] Dawid Weiss commented on LUCENE-3832: - It'd be possible to avoid the sort and still m

Re: Thread "leaking" in junit tests

> I absolutely agree, even though IMO warning is better than silence. I plan to work on it soon, we've released Carrot2 and Lingo3G and there's a chunk of free time for me to work on randomized testing. > Anyway I got what I wanted: a failure in my test ;) So maybe I'll hint you a bit more -- lo

Re: Thread "leaking" in junit tests

On Fri, Jun 29, 2012 at 12:01 PM, Dawid Weiss wrote: > My pleasure. Dealing with leaked threads is a tough area and it needs > to be addressed at some point sooner or later. The warnings are not > enough because nobody looks at them (for example in jenkins runs). > Tests (suites) simply shouldn't

[JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 311 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/311/ All tests passed Build Log: [...truncated 14319 lines...] BUILD FAILED /mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux-Java6-64/checkout/build.xml:62: The following error occurred while executing this line: /mnt/

[jira] [Resolved] (LUCENE-4160) Bring back the functional equivalent of tests.iters.min

[ https://issues.apache.org/jira/browse/LUCENE-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss resolved LUCENE-4160. - Resolution: Fixed Fix Version/s: 4.0 > Bring back the functional equivalent of tests.

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 14796 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14796/ All tests passed Build Log: [...truncated 19528 lines...] [...truncated 19409 lines...] rat-sources: [echo] [echo] * [echo] Summary [echo] ---

Re: Thread "leaking" in junit tests

My pleasure. Dealing with leaked threads is a tough area and it needs to be addressed at some point sooner or later. The warnings are not enough because nobody looks at them (for example in jenkins runs). Tests (suites) simply shouldn't leak threads, period (yes, it is my idee fixe to have this don

Re: Thread "leaking" in junit tests

Thanks for the detailed explanation Dawid! -- Sami Siren On Fri, Jun 29, 2012 at 11:14 AM, Dawid Weiss wrote: >> WARNING: test class left thread running: >> Thread[MultiThreadedHttpConnectionManager cleanup,5,main] >> >> I do not see such warnings in 4.x or trunk, how do I enable such warnings

[jira] [Created] (LUCENE-4181) Change the semantics of @Slow on tests

Dawid Weiss created LUCENE-4181: --- Summary: Change the semantics of @Slow on tests Key: LUCENE-4181 URL: https://issues.apache.org/jira/browse/LUCENE-4181 Project: Lucene - Java Issue Type: Task

[JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 1091 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/1091/ All tests passed Build Log: [...truncated 14206 lines...] BUILD FAILED /mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Linux-Java6-64/checkout/build.xml:62: The following error occurred while executing this line:

Use of @Slow annotation on tests

Hi. I would like to change the use of @Slow. Currently only this test: Test2BTerms#test2BTerms is annotated with this annotation. I don't know how slow it really is, but I would like to: * change this particular test to @Ignore or give it an assumption inside, * change the annotation group @Slo

[JENKINS] Lucene-Solr-tests-only-4.x-java7 - Build # 70 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x-java7/70/ All tests passed Build Log: [...truncated 20607 lines...] [...truncated 20497 lines...] rat-sources: [echo] [echo] * [echo] Summary [echo] ---

[jira] [Updated] (LUCENE-4171) Performance improvements to Packed64

[ https://issues.apache.org/jira/browse/LUCENE-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toke Eskildsen updated LUCENE-4171: --- Attachment: LUCENE-4171.patch Attached patch with constructor #1 size calculation change. Un

[JENKINS] Lucene-Solr-trunk-Linux-Java7-64 - Build # 444 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java7-64/444/ 1 tests failed. FAILED: org.apache.lucene.util.TestMaxFailuresRule.testMaxFailures Error Message: expected:<2> but was:<0> Stack Trace: java.lang.AssertionError: expected:<2> but was:<0> at org.junit.As

Re: Thread "leaking" in junit tests

> WARNING: test class left thread running: > Thread[MultiThreadedHttpConnectionManager cleanup,5,main] > > I do not see such warnings in 4.x or trunk, how do I enable such warnings > there? Open LuceneTestCase and change this attribute to true: @ThreadLeaks(failTestIfLeaking = false) this will

[JENKINS] Lucene-Solr-4.x-Linux-Java7-64 - Build # 268 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java7-64/268/ All tests passed Build Log: [...truncated 15312 lines...] BUILD FAILED /mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux-Java7-64/checkout/build.xml:62: The following error occurred while executing this line: /mnt/

Thread "leaking" in junit tests

Hi, In 3.x when a Solr test case leaves threads running there's a warning printed like this: WARNING: test class left thread running: Thread[MultiThreadedHttpConnectionManager cleanup,5,main] I do not see such warnings in 4.x or trunk, how do I enable such warnings there? -- Sami Siren --

[JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 310 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/310/ All tests passed Build Log: [...truncated 14343 lines...] BUILD FAILED /mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux-Java6-64/checkout/build.xml:62: The following error occurred while executing this line: /mnt/

Re: regular but not individually reproducible failure: TestIndexWriterWithThreads.testRollbackAndCommitWithThreads

this seems like a windows / files issue. We can not obtain the write lock quickly enough. Maybe we should do a retry loop in the test if we are on windows? simon On Thu, Jun 28, 2012 at 6:25 PM, Steven A Rowe wrote: > I see this roughly 50% of the time I run all Lucene core tests (Win7 64, Sun

Re: Make ivy search maven repo1/repo2?

I don't know what you mean by "use it from Solr" but I guess regular targets to assemble the example/ solr distribution will update Lucene jars. So ant example or dist* should work. Dawid On Thu, Jun 28, 2012 at 9:21 PM, Lance Norskog wrote: > The ant build. I have added a new Lucene class and w

Re: [JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 1090 - Failure!

I've seen this one on my build server too. Dawid On Fri, Jun 29, 2012 at 9:19 AM, Policeman Jenkins Server wrote: > Build: > http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/1090/ > > 1 tests failed. > REGRESSION:   > org.apache.lucene.analysis.ngram.NGramTokenizerTest.te

[JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 1090 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/1090/ 1 tests failed. REGRESSION: org.apache.lucene.analysis.ngram.NGramTokenizerTest.testRandomStrings Error Message: some thread(s) failed Stack Trace: java.lang.RuntimeException: some thread(s) failed at

  1   2   >