[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485582#comment-13485582 ] Alan Woodward commented on LUCENE-2878: --- I committed a few more javadoc fixes. Ant

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485584#comment-13485584 ] Simon Willnauer commented on LUCENE-2878: - bq. I committed a few more javadoc fix

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485585#comment-13485585 ] Alan Woodward commented on LUCENE-2878: --- > I'd rename the package o.a.l.s.positions

Jenkins build is back to normal : fast-io-beasting #6101

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

Re: [JENKINS] Lucene-Solr-Tests-trunk-java7 - Build # 3346 - Still Failing

Ok, committed an upgrade to 2.0.4. I'm leaving for a few hours; should anything go wrong (not likely, but always a possibility) please revert my latest commit. Dawid On Sat, Oct 27, 2012 at 10:05 PM, Dawid Weiss wrote: >> Yes, I'll spin an update of randomizedtesting as soon as I fix this. > > O

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485594#comment-13485594 ] Simon Willnauer commented on LUCENE-2878: - I renamed the package and fixed the pa

[JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.7.0_07) - Build # 2049 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux/2049/ Java: 32bit/jdk1.7.0_07 -server -XX:+UseG1GC 1 tests failed. REGRESSION: org.apache.lucene.analysis.core.TestRandomChains.testRandomChains Error Message: last stage: inconsistent startOffset at pos=0: 0 vs 2; token=cjpjt

Re: Source Control

On Sun, Oct 28, 2012 at 2:59 AM, Michael Wechner wrote: > I also had/have quite some trouble to get used to the git commandline, > although or maybe because I used SVN commandline for many years, but I am > very glad now to be using git on other projects, because in particular the > process in be

Build failed in Jenkins: slow-io-beasting #4977

See -- [...truncated 10829 lines...] [junit4:junit4] [junit4:junit4] Suite: org.apache.lucene.search.suggest.analyzing.AnalyzingSuggesterTest [junit4:junit4] Completed on J4 in 2.59s, 14 t

Re: [JENKINS] Lucene-Solr-Tests-trunk-java7 - Build # 3346 - Still Failing

I got another hang (heartbeat in ""), but i couldnt use jstack (access denied, even as root!) on the forked jvm. the other jvms worked fine. because jenkins was killed, it decided to erase all evidence any of this happened: http://sierranevada.servebeer.com:8080/job/slow-io-beasting/ (There is a 4

Re: LUCENE-2878 aka. positions branch

Can you make a patch for review, showing the differences between the trunk and branch? On Sun, Oct 28, 2012 at 5:43 AM, Simon Willnauer wrote: > hey folks, > > alan and myself cleaned up the positions branch to get it ready for > reintegration into trunk. I'm kindly asking everybody who as intere

Jenkins build is back to normal : slow-io-beasting #4979

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

[jira] [Updated] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Willnauer updated LUCENE-2878: Attachment: LUCENE-2878-vs-trunk.patch here is a diff against trunk for better reviewing

Re: LUCENE-2878 aka. positions branch

On Sun, Oct 28, 2012 at 11:10 AM, Robert Muir wrote: > Can you make a patch for review, showing the differences between the > trunk and branch? I attached one to the issue! --> https://issues.apache.org/jira/secure/attachment/12551113/LUCENE-2878-vs-trunk.patch simon > > On Sun, Oct 28, 2012 at

Build failed in Jenkins: fast-io-beasting #6120

See -- [...truncated 12597 lines...] [junit4:junit4] 2>at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947) [junit4:junit4] 2>at java.util

Re: Source Control

Am 28.10.12 10:57, schrieb Robert Muir: On Sun, Oct 28, 2012 at 2:59 AM, Michael Wechner wrote: I also had/have quite some trouble to get used to the git commandline, although or maybe because I used SVN commandline for many years, but I am very glad now to be using git on other projects, bec

Build failed in Jenkins: slow-io-beasting #4982

See -- [...truncated 14009 lines...] [junit4:junit4] 2> 694989 T17 oazs.NIOServerCnxn.closeSock Closed socket connection for client /127.0.0.1:57720 which had sessionid 0x13aa7129a150002

Jenkins build is back to normal : slow-io-beasting #4983

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

Re: Source Control

What I wish we could do is to truly collaborate on these branches. For instance, when we create a feature branch today (following an issue), then people are free to commit changes to the branch, without worrying about breaking the main branch or nightly builds. When it's time, the changes will be m

[jira] [Commented] (SOLR-1972) Need additional query stats in admin interface - median, 95th and 99th percentile

[ https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485613#comment-13485613 ] Adrien Grand commented on SOLR-1972: In that case could we use something else than the

Build failed in Jenkins: slow-io-beasting #4985

See -- [...truncated 25804 lines...] [junit4:junit4] [junit4:junit4] Suite: org.apache.solr.handler.FieldAnalysisRequestHandlerTest [junit4:junit4] Completed on J3 in 2.65s, 4 tests [junit4

Jenkins build is back to normal : slow-io-beasting #4986

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

Re: Source Control

I don't have stropng feelings either way. If it would allow better collaboration branch merging, etc., then sure. I'm assuming we'd be able to do pre/post move diffs, right?. What about reformatting at that point? It'd be one of the few times when we would, I think, have all the code in the repos

Build failed in Jenkins: fast-io-beasting #6121

See -- [...truncated 13484 lines...] [junit4:junit4] 2> 752 T81 oasc.SolrCore.decrefSolrCoreState Closing SolrCoreState [junit4:junit4] 2> 753 T81 oasu.DefaultSolrCoreState.closeInde

Jenkins build is back to normal : fast-io-beasting #6122

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

Build failed in Jenkins: slow-io-beasting #4989

See -- [...truncated 13817 lines...] [junit4:junit4] 2> commit{dir=MockDirWrapper(org.apache.lucene.store.NIOFSDirectory@

Build failed in Jenkins: slow-io-beasting #4990

See -- [...truncated 13823 lines...] [junit4:junit4] 2> 29933 T10 oass.IndexSchema.readSchema unique key field: id [junit4:junit4] 2> 29933 T10 oasc.SolrCore. [collection1] Opening new

Build failed in Jenkins: slow-io-beasting #4991

See -- [...truncated 13902 lines...] [junit4:junit4] 2> 30038 T10 oashl.XMLLoader.init xsltCacheLifetimeSeconds=60 [junit4:junit4] 2> 30053 T10 oass.SolrIndexSearcher. Opening Searcher@

Jenkins build is back to normal : slow-io-beasting #4992

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

[jira] [Resolved] (SOLR-880) SolrCore should have a a lazy startup option

[ https://issues.apache.org/jira/browse/SOLR-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson resolved SOLR-880. - Resolution: Duplicate This functionality will be part of SOLR-1028, which will be checked in shortl

[jira] [Resolved] (LUCENE-3319) Cut over remaining queries to provide PositionIterators

[ https://issues.apache.org/jira/browse/LUCENE-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Willnauer resolved LUCENE-3319. - Resolution: Fixed tracked in the toplevel issue and resolved except of MultiPhraseQuery

Typo in _version_ error message

The _version_ error message is missing a space between _version_ and “field”: Oct 28, 2012 10:24:34 AM org.apache.solr.update.UpdateLog init SEVERE: Unable to use updateLog: _version_field must exist in schema, using indexed="true" stored="true" and multiValued="false" (_version_ does not exist)

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485637#comment-13485637 ] Michael McCandless commented on LUCENE-2878: I'm still trying to catch up her

[jira] [Commented] (SOLR-1972) Need additional query stats in admin interface - median, 95th and 99th percentile

[ https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485639#comment-13485639 ] Alan Woodward commented on SOLR-1972: - The toString() is sort of a randomly-generated s

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485640#comment-13485640 ] Michael McCandless commented on LUCENE-2878: I'm confused on how one uses Int

[jira] [Commented] (SOLR-1972) Need additional query stats in admin interface - median, 95th and 99th percentile

[ https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485641#comment-13485641 ] Adrien Grand commented on SOLR-1972: Can it break if people write custom request handle

Re: Source Control

We have an official git mirror for the project, though - git.apache.org/lucene-solr. So if people want to use git to collaborate, they can clone that repository and create branches there. I much prefer git to svn - I use staged adds, rebases and stashes all the time - but anyone can currently

[jira] [Commented] (SOLR-1972) Need additional query stats in admin interface - median, 95th and 99th percentile

[ https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485643#comment-13485643 ] Alan Woodward commented on SOLR-1972: - I suppose if we had two custom request handlers

[jira] [Commented] (SOLR-1972) Need additional query stats in admin interface - median, 95th and 99th percentile

[ https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485645#comment-13485645 ] Adrien Grand commented on SOLR-1972: After reading the documentation of {{Object.toStri

[jira] [Assigned] (SOLR-1533) Partition data directories into multiple "bucket" directories

[ https://issues.apache.org/jira/browse/SOLR-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson reassigned SOLR-1533: Assignee: Erick Erickson > Partition data directories into multiple "bucket" directories

Build failed in Jenkins: slow-io-beasting #4997

See -- [...truncated 13878 lines...] [junit4:junit4] 2> 26695 T10 oashc.HttpShardHandlerFactory.getParameter Setting sizeOfQueue to: -1 [junit4:junit4] 2> 26695 T10 oashc.HttpShardHandl

Re: Source Control

On 10/28/2012 11:09 AM, Alan Woodward wrote: We have an official git mirror for the project, though - git.apache.org/lucene-solr. So if people want to use git to collaborate, they can clone that repository and create branches there. I much prefer git to svn - I use staged adds, rebases and st

[jira] [Commented] (SOLR-1533) Partition data directories into multiple "bucket" directories

[ https://issues.apache.org/jira/browse/SOLR-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485656#comment-13485656 ] Erick Erickson commented on SOLR-1533: -- I'm thinking of killing this JIRA, SOLR-1306 (

Re: Source Control

This has come up in discussion at the ASF. I think a couple people thought the check box was critical. I think some higher level people said that is bs. The important part still comes down to the committer committing code that has been properly contributed. You don't need a checkbox for that, an

Build failed in Jenkins: fast-io-beasting #6138

See -- [...truncated 13310 lines...] [junit4:junit4] 2> 87794 T10 oazs.FinalRequestProcessor.shutdown shutdown of request processor complete [junit4:junit4] 2> 87794 T10 oasc.ChaosMonkey.mon

[JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 27 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/27/ No tests ran. Build Log: [...truncated 30432 lines...] prepare-release-no-sign: [mkdir] Created dir: /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeRelease [copy] Copying 396

Jenkins build is back to normal : fast-io-beasting #6139

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

Re: Build failed in Jenkins: fast-io-beasting #6138

I tried raising the timeout a bit here since this seems to be intermittent. On Oct 28, 2012, at 12:08 PM, Charlie Cron wrote: > See > > -- > [...truncated 13310 lines...] > [junit4:junit4] 2

Build failed in Jenkins: slow-io-beasting #4998

See -- [...truncated 479927 lines...] [junit4:junit4] 2> 1050031 T245 oazs.NIOServerCnxn.closeSock Closed socket connection for client /127.0.0.1:50577 which had sessionid 0x13aa81b3d0800

Re: [JENKINS] Lucene-Solr-Tests-trunk-java7 - Build # 3346 - Still Failing

> I got another hang (heartbeat in ""), but i couldnt use > jstack (access denied, even as root!) on the forked jvm. the other We observed something like this a few times on FreeBSD. Might be a JVM issue, hard to tell. I'm testing a hung shutdown hook and it passes on all my testing environments (

Re: Source Control

Can we put a notice on the github page that essentially says “ownership of any code committed to this repo is implicitly transferred to ASF”? -- Jack Krupansky From: Mark Miller Sent: Sunday, October 28, 2012 12:01 PM To: dev@lucene.apache.org Subject: Re: Source Control This has come up in d

RE: Source Control

I don't want to use GIT; HG was horrible, too! - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Mark Miller [mailto:markrmil...@gmail.com] > Sent: Saturday, October 27, 2012 1:02 AM > To: dev@lucene.apach

Jenkins build is back to normal : slow-io-beasting #4999

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

Re: Source Control

Hi Uwe, On Sun, Oct 28, 2012 at 5:25 PM, Uwe Schindler wrote: > I don't want to use GIT; HG was horrible, too! Why don't you like them? -- Adrien - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional comm

Re: Source Control

Different toys for different boys. Everyone will have his or her favorite workflow, it'll be impossible to find a consensus here. As for me, I've tasted cvs, svn, git and other version control systems and I must say git is the one I like the most, although there were a good few cursing moments alon

[jira] [Updated] (SOLR-1028) Automatic core loading unloading for multicore

[ https://issues.apache.org/jira/browse/SOLR-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated SOLR-1028: - Attachment: SOLR-1028.patch Patch attached. This will subsume SOLR-880, keeping them separate was

Build failed in Jenkins: fast-io-beasting #6143

See -- [...truncated 13408 lines...] [junit4:junit4] 2> 674313 T548 oasu.DefaultSolrCoreState.closeIndexWriter SolrCoreState ref count has reached 0 - closing IndexWriter [junit4:junit4] 2>

Jenkins build is back to normal : fast-io-beasting #6144

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

Build failed in Jenkins: slow-io-beasting #5002

See -- [...truncated 13818 lines...] [junit4:junit4] 2> 32509 T10 oasc.SolrResourceLoader.locateSolrHome JNDI not configured for solr (NoInitialContextEx) [junit4:junit4] 2> 32509 T10 o

Build failed in Jenkins: slow-io-beasting #5003

See -- [...truncated 13925 lines...] [junit4:junit4] 2> 27554 T10 oass.IndexSchema.readSchema unique key field: id [junit4:junit4] 2> 27554 T10 oasc.SolrCore. [collection1] Opening new

[jira] [Commented] (SOLR-1028) Automatic core loading unloading for multicore

[ https://issues.apache.org/jira/browse/SOLR-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485679#comment-13485679 ] Erick Erickson commented on SOLR-1028: -- Here are the comments I _meant_ to include. 1

Jenkins build is back to normal : slow-io-beasting #5004

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

[jira] [Commented] (SOLR-1028) Automatic core loading unloading for multicore

[ https://issues.apache.org/jira/browse/SOLR-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485683#comment-13485683 ] Mark Miller commented on SOLR-1028: --- Kind of an aside to this specific issue, but in rela

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485685#comment-13485685 ] Simon Willnauer commented on LUCENE-2878: - thanks mike for taking a look at this.

Build failed in Jenkins: fast-io-beasting #6154

See -- [...truncated 24164 lines...] [junit4:junit4] 2> 112510 T18 oasu.DefaultSolrCoreState.closeIndexWriter closing IndexWriter with IndexWriterCloser [junit4:junit4] 2> 112512 T18 oasc.So

Jenkins build is back to normal : fast-io-beasting #6155

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

Re: FuzzyQuery vs SlowFuzsyQuery docs? -- was: Re: [jira] [Commented] (LUCENE-2667) Fix FuzzyQuery's defaults, so its fast.

+1 !!! Also a BIG +1 for leaving the old logic around. I've been discussing this with a client, on behalf of their clients. They're fine with the slower speed, and they need the option of lower percentage matches, which they combine with other business logic, to insure acceptable matches. ***My

Are the Solr BCD field types still supported?

I was going through the Solr field types and ran across the “BCD” field types. They are not mentioned in the Solr Schema wiki and have no Javadoc. Are they really supported anymore? Should they be deprecated? They are NOT marked as “legacy” field types. If they are to be supported, will anybody

[jira] [Created] (SOLR-4004) Improve Javadoc for SolrPing

Benson Margulies created SOLR-4004: -- Summary: Improve Javadoc for SolrPing Key: SOLR-4004 URL: https://issues.apache.org/jira/browse/SOLR-4004 Project: Solr Issue Type: Improvement

[jira] [Updated] (SOLR-4004) Improve Javadoc for SolrPing

[ https://issues.apache.org/jira/browse/SOLR-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated SOLR-4004: --- Description: There's no text in the javadoc of SolrPing. Since it depends on a particular adm

what's up, doc?

Folks, I'm going to go out on an egotistical limb and ask you all if you would consider making me a committer based on my slow but steady drip of javadoc patches. If you don't, I'll still keep tossing in patches. My experience is that every time I do a round of applying myself to Solr, I trip ov

[jira] [Updated] (SOLR-1972) Need additional query stats in admin interface - median, 95th and 99th percentile

[ https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward updated SOLR-1972: Attachment: SOLR-1972_metrics.patch In this patch, the scope name is generated from a static AtomicL

[jira] [Updated] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2878: --- Attachment: LUCENE-2878.patch This is what I had in mind to remove PostingFeatures.i

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

[ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485723#comment-13485723 ] Michael McCandless commented on LUCENE-2878: {quote} bq. I'm confused on how

[jira] [Assigned] (SOLR-4004) Improve Javadoc for SolrPing

[ https://issues.apache.org/jira/browse/SOLR-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward reassigned SOLR-4004: --- Assignee: Alan Woodward > Improve Javadoc for SolrPing > > >

[jira] [Resolved] (SOLR-4004) Improve Javadoc for SolrPing

[ https://issues.apache.org/jira/browse/SOLR-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward resolved SOLR-4004. - Resolution: Fixed Fix Version/s: 5.0 4.1 Committed, trunk: 1403109, bran

[jira] [Closed] (SOLR-3983) Test failure in SoftAutoCommitTest

[ https://issues.apache.org/jira/browse/SOLR-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward closed SOLR-3983. --- Resolution: Not A Problem Doesn't reproduce if my IDE isn't running. > Test failure i

Build failed in Jenkins: slow-io-beasting #5018

See Changes: [romseygeek] SOLR-4004: Improve Javadoc for SolrPing -- [...truncated 14045 lines...] [junit4:junit4] 2> 28744 T10 oashc.HttpShardHandlerFactory.getParameter Setting

Jenkins build is back to normal : slow-io-beasting #5019

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

Build failed in Jenkins: fast-io-beasting #6178

See -- [...truncated 12597 lines...] [junit4:junit4] 2>at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) [junit4:junit4] 2>at sun.nio.ch.EPollArrayWrapper.pol

Jenkins build is back to normal : fast-io-beasting #6179

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

Build failed in Jenkins: slow-io-beasting #5020

See -- [...truncated 14006 lines...] [junit4:junit4] 2> 690757 T282 oazs.NIOServerCnxn.closeSock Closed socket connection for client /127.0.0.1:58646 which had sessionid 0x13aa99d68d2

Re: Source Control

If Lucene was moved to use GIT, I would love that. Not going into details now, but having used GIT for two years on other open source projects I'm pretty sure that it makes collaboration significantly easier. We use GitHub, but the star is GIT: GitHub makes it easier for non-power users and is gre

Jenkins build is back to normal : slow-io-beasting #5021

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

Re: Build failed in Jenkins: slow-io-beasting #5020

This is happening right at the start of the test - so all the nodes are not showing up as ready as part of the setup - before the test even starts. I've added some test code to print the zk tree and all the current thread stack traces when this times out. - Mark On 10/28/2012 07:17 PM, Charl

Build failed in Jenkins: slow-io-beasting #5023

See -- [...truncated 13977 lines...] [junit4:junit4] 2> 686941 T216 oaz.ClientCnxn$SendThread.run Unable to read additional data from server sessionid 0x13aa9d8483b0002, likely server has

[jira] [Created] (SOLR-4005) If CoreContainer fails to register a created core, it should close it.

Mark Miller created SOLR-4005: - Summary: If CoreContainer fails to register a created core, it should close it. Key: SOLR-4005 URL: https://issues.apache.org/jira/browse/SOLR-4005 Project: Solr

Jenkins build is back to normal : slow-io-beasting #5024

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

[jira] [Created] (SOLR-4006) Many tests on Apache Jenkins are failing with lingering threads.

Mark Miller created SOLR-4006: - Summary: Many tests on Apache Jenkins are failing with lingering threads. Key: SOLR-4006 URL: https://issues.apache.org/jira/browse/SOLR-4006 Project: Solr Issue

[jira] [Commented] (SOLR-4006) Many tests on Apache Jenkins are failing with lingering threads.

[ https://issues.apache.org/jira/browse/SOLR-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485766#comment-13485766 ] Mark Miller commented on SOLR-4006: --- The good news is, I can duplicate this on my FreeBSD

Build failed in Jenkins: fast-io-beasting #6191

See -- [...truncated 13491 lines...] [junit4:junit4] 2> 89052 T359 oasu.DefaultSolrCoreState.closeIndexWriter closing IndexWriter with IndexWriterCloser [junit4:junit4] 2> 89053 T359 oasc.So

Re: Build failed in Jenkins: fast-io-beasting #6191

So the issue here appears to be: [junit4:junit4] 2> 72153 T359 oasc.SolrException.log SEVERE null:org.apache.solr.common.SolrException: Could not get shard_id for core: collection1 [junit4:junit4] 2> at org.apache.solr.cloud.ZkController.doGetShardIdProcess(ZkController.jav

Jenkins build is back to normal : fast-io-beasting #6192

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

Re: Source Control

+1 I'm definitely in favor of moving to git. I've gotten past the learning curve hurdle and I appreciate its benefits. The real challenge, I think, is figuring out how we can get real collaboration like what is possible on GitHub, without actually truly being on GitHub. Maybe Atlassian's new Sta

Build failed in Jenkins: slow-io-beasting #5028

See -- [...truncated 13895 lines...] [junit4:junit4] 2> commit{dir=MockDirWrapper(org.apache.lucene.store.NIOFSDirectory@

Build failed in Jenkins: slow-io-beasting #5029

See -- [...truncated 13806 lines...] [junit4:junit4] 2> 28247 T10 oasc.CoreContainer.create Creating SolrCore 'collection1' using instanceDir: .\org.apache.solr.client.solrj.TestLBHttpSo

Jenkins build is back to normal : slow-io-beasting #5030

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

Build failed in Jenkins: slow-io-beasting #5032

See -- [...truncated 13130 lines...] [junit4:junit4] 2> 20719 T506 oasc.RequestHandlers.initHandlersFromConfig created standard: solr.StandardRequestHandler [junit4:junit4] 2> 20719 T50

Jenkins build is back to normal : slow-io-beasting #5033

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

Build failed in Jenkins: fast-io-beasting #6196

See -- [...truncated 13475 lines...] [junit4:junit4] 2> 7222463 T114 oascc.SolrZkClient.makePath makePath: /overseer_elect/election [junit4:junit4] 2> 7222471 T150 oazs.PrepRequestProcessor.

  1   2   >