Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java6-64/784/
1 tests failed.
REGRESSION:
org.apache.lucene.facet.taxonomy.directory.TestDirectoryTaxonomyWriter.testConcurrency
Error Message:
mismatch number of categories expected:<25402> but was:<25407>
Stack Trace:
j
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/328/
1 tests failed.
REGRESSION: org.apache.solr.spelling.suggest.SuggesterFSTTest.testRebuild
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
at
__rand
[
https://issues.apache.org/jira/browse/SOLR-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-3460.
---
Resolution: Fixed
This is in.
> Improve cmd line config bootstrap tool.
> ---
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414169#comment-13414169
]
Mark Miller commented on SOLR-3619:
---
bq. so anything we provide OOTB will per definition
> I would go down the route and would supply Solr with a high-performance
> network layer (like netty) without any Servlet Crap.
Yea, that would certainly be an interesting path to explore and a more
attractive way to morph Solr into a standalone server than being a Jetty-only
webapp. It would
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414142#comment-13414142
]
Jan Høydahl commented on SOLR-3619:
---
The name "server" is good in that it indicate that t
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414107#comment-13414107
]
Nikola Tankovic commented on LUCENE-3312:
-
Not at the moment, just little more ti
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414105#comment-13414105
]
Mark Miller commented on SOLR-3619:
---
We really need that per version doc - the biggest pa
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414102#comment-13414102
]
Uwe Schindler commented on LUCENE-3312:
---
Is there anything at the moment you need h
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414100#comment-13414100
]
Nikola Tankovic commented on LUCENE-3312:
-
Hi Uwe,
in a few days I will hopeful
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414097#comment-13414097
]
Uwe Schindler commented on LUCENE-3312:
---
Hi Nikola,
the second half of the GSoC sta
[
https://issues.apache.org/jira/browse/LUCENE-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4217:
--
Attachment: LUCENE-4217.patch
Final patch. I added exclusion of the license from src.tgz files
[
https://issues.apache.org/jira/browse/SOLR-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-3328:
Fix Version/s: (was: 4.1)
5.0
4.0
3.6.1
[
https://issues.apache.org/jira/browse/SOLR-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414089#comment-13414089
]
Uwe Schindler commented on SOLR-3328:
-
I committed a partial fix, needs further verific
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414086#comment-13414086
]
Mark Miller commented on SOLR-3619:
---
Work with these kinds of moves gets out dated quickl
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3619:
--
Attachment: SOLR-3619.patch
first cut patch
> Rename 'example' dir to 'server'
> --
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414085#comment-13414085
]
Mark Miller commented on SOLR-3619:
---
obviously will use svn moves though despite patch
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3619:
--
Attachment: server-name-layout.png
This what my proposed layout would look.
> Rename 'e
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/1247/
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestSnapshotDeletionPolicy.testMultiThreadedSnapshotting
Error Message:
Snapshot doesn't exist: t1
Stack Trace:
java.lang.IllegalStateException: Snapshot do
See https://issues.apache.org/jira/browse/SOLR-3620
On Fri, Jul 13, 2012 at 11:46 AM, Uwe Schindler wrote:
> ...and I wanted to inform you it is hanging again in Solr! Who can help to
> solve this issue?
>
> http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java7-64/400/console
>
> Uw
[
https://issues.apache.org/jira/browse/SOLR-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413958#comment-13413958
]
Mikhail Khludnev commented on SOLR-1725:
Hoss,
Congrats! Btw, have you seen one mo
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Han Jiang updated LUCENE-3892:
--
Attachment: (was: LUCENE-3892-for&pfor-with-javadoc.patch)
> Add a useful intblock postings fo
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Han Jiang updated LUCENE-3892:
--
Attachment: LUCENE-3892-for&pfor-with-javadoc.patch
bq. Instead of having P/ForUtil reach up into P/Fo
[
https://issues.apache.org/jira/browse/SOLR-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413936#comment-13413936
]
Mark Miller commented on SOLR-3620:
---
I've committed an attempted fix.
>From what I can t
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Han Jiang updated LUCENE-3892:
--
Attachment: LUCENE-3892-for&pfor-with-javadoc.patch
> Add a useful intblock postings format (eg, F
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413935#comment-13413935
]
Michael McCandless commented on LUCENE-3892:
Those are interesting results!
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Han Jiang updated LUCENE-3892:
--
Attachment: (was: LUCENE-3892-for&pfor-with-javadoc.patch)
> Add a useful intblock postings fo
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java7-64/527/
1 tests failed.
REGRESSION: org.apache.solr.spelling.suggest.SuggesterFSTTest.testRebuild
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
at
__ra
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Han Jiang updated LUCENE-3892:
--
Attachment: LUCENE-3892-for&pfor-with-javadoc.patch
previous patch is a little messy, do some cleanups
[
https://issues.apache.org/jira/browse/LUCENE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4219:
Attachment: LUCENE-4219_test.patch
> PayloadNearQuery bugs
> -
>
>
Robert Muir created LUCENE-4219:
---
Summary: PayloadNearQuery bugs
Key: LUCENE-4219
URL: https://issues.apache.org/jira/browse/LUCENE-4219
Project: Lucene - Java
Issue Type: Bug
Repor
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java7-64/286/
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestIndexWriterWithThreads.testOpenTwoIndexWritersOnDifferentThreads
Error Message:
Failed due to: org.apache.lucene.store.LockObtainFailedException: Lock obt
: (1) The actual metadata posted is a string of the form "12345;#string".
: There is only be one value posted for the metadata field, but Solr
: complains that we're trying to apply multiple values to a single-valued
: field and does not index the document, unless the ";" is removed. That
:
[
https://issues.apache.org/jira/browse/SOLR-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413873#comment-13413873
]
Mark Miller commented on SOLR-3620:
---
I think I have a handle on the issue. Some of my tes
[
https://issues.apache.org/jira/browse/SOLR-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-3620:
-
Assignee: Mark Miller
> Almost every test relating to cloud hangs since July 12, 2012
> --
[
https://issues.apache.org/jira/browse/SOLR-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413842#comment-13413842
]
Mark Miller commented on SOLR-3620:
---
Hmm...I'll take a look. I committed some stuff so I
Uwe Schindler created SOLR-3620:
---
Summary: Almost every test relating to cloud hangs since July 12,
2012
Key: SOLR-3620
URL: https://issues.apache.org/jira/browse/SOLR-3620
Project: Solr
Issue
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413781#comment-13413781
]
Han Jiang edited comment on LUCENE-3892 at 7/13/12 4:00 PM:
T
In addition:
Solr is *not* and J2EE application! It just uses the servlet container to have
a connection to outside. Installing Solr is JBoss or any other full fledged
J2EE container is a waste of resources and controllability.
I would go down the route and would supply Solr with a high-performa
Whatever we do, we should never, never, never make it more difficult
to get Solr running for the first time than what we do now... Hmmm,
sounds like I think it's hard to start it the first time. It's not,
it's super-easy and we _must not_ lose that. Not saying that anyone
proposes making it harder,
On Jul 13, 2012, at 11:37 AM, Dyer, James wrote:
> But I don't see why we need to be naming our parameters "JettyThis" or
> "JettyThat" and telling people they've got to use Jetty.
We are not naming parameters jetty this or jetty that - we are pre configuring
solr.xml to pick up the jetty por
On Fri, Jul 13, 2012 at 11:37 AM, Dyer, James wrote:
> On the other hand, expecting to test every possible container before you can
> tell people its "supported" for a standards-compliant java web-app is just
> crazy. This is like saying that DIH's SQLEntityProcessor is only supported
> for HS
On Tue, 10 Jul 2012, Andi Vajda wrote:
I would also like to propose a change, to allow for more flexible
mechanism of generating Python class names. The patch doesn't change
the default pylucene behaviour, but it gives people a way to replace
class names with patterns. I have noticed that there
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java7-64/400/
All tests passed
Build Log:
[...truncated 17531 lines...]
[junit4:junit4] 2012-07-13 15:45:40
[junit4:junit4] Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.0-b21
mixed mode):
[junit4:junit4]
[junit4:juni
...and I wanted to inform you it is hanging again in Solr! Who can help to
solve this issue?
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java7-64/400/console
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Orig
>From my perspective, working for a company that uses Solr on a bunch of apps,
>I really wish we keep it agnostic. I see the case for documenting that "our
>testing process exclusively uses Jetty 7, we've included it in our
>distribution, and we recommend it". But I don't see why we need to be
[
https://issues.apache.org/jira/browse/SOLR-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-3600.
---
Resolution: Fixed
> We should consider raising our default ZooKeeper session timeout.
> --
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413806#comment-13413806
]
Mark Miller commented on SOLR-3619:
---
So I guess as I look at things, this would be my fir
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4211.
-
Resolution: Fixed
Fix Version/s: 5.0
4.0
> in LuceneTestCase.maybe
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/323/
1 tests failed.
REGRESSION: org.apache.lucene.util.TestMaxFailuresRule.testMaxFailures
Error Message:
Stack Trace:
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:92)
at org.junit
Build: https://builds.apache.org/job/Solr-4.x/36/
1 tests failed.
REGRESSION: org.apache.solr.cloud.RecoveryZkTest.testDistribSearch
Error Message:
Thread threw an uncaught exception, thread: Thread[Lucene Merge Thread #1,6,]
Stack Trace:
java.lang.RuntimeException: Thread threw an uncaught exc
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Han Jiang updated LUCENE-3892:
--
Attachment: LUCENE-3892-for&pfor-with-javadoc.patch
This patch cut the extra header and merge numBytes
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4211:
Attachment: LUCENE-4211.patch
updated patch. I think its ready for committing, finally.
[
https://issues.apache.org/jira/browse/SOLR-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413775#comment-13413775
]
Mark Miller commented on SOLR-3215:
---
Okay, I'm going to put this in. I'll wait a bit to s
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413773#comment-13413773
]
Robert Muir commented on LUCENE-4211:
-
OK, the problem is in their reset(), doesnt re
I believe it's because the default is for SolrCloud where you will have
replicas of the info for recovery and so it's just overkill. The tran log
is still used for other things (realtime get, peer sync - it may play a
part in other features).
We should probably doc this well so that single node us
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4211:
Attachment: LUCENE-4211.patch
Latest patch: with all randomization turned back on, but also fixing
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413749#comment-13413749
]
Robert Muir commented on LUCENE-4211:
-
You are right: thats the bug. Ill also add ass
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413745#comment-13413745
]
Michael McCandless commented on LUCENE-4211:
In AssertingDocsAndPositionsEnum
There was a thread a couple months back:
http://markmail.org/thread/7w3z2lsgb7fpfewb
That didn't reach closure, so I want to re-raise / answer it:
It seems like SyncLevel defaults to FLUSH not SYNC in Solr's
TransactionLog? Is that still true in Lucene 4.0 alpha?
Does this really mean on O
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413739#comment-13413739
]
Robert Muir commented on LUCENE-4211:
-
Just as i say that:
{noformat}
ant test -Dtes
[
https://issues.apache.org/jira/browse/LUCENE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413733#comment-13413733
]
Chris Male commented on LUCENE-4173:
I do quite like this idea.
Couple of thoughts
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4211:
Attachment: LUCENE-4211.patch
final patch: all tests pass. Thanks Mike!
> in Luce
On Jul 13, 2012, at 9:19 AM, Robert Muir wrote:
> I know the wiki used to
> say the release manager should go and manually test alternative
> containers before releasing: I refuse to do that. Its not the release
> manager's job.
That's insane anyhow :) The RM can't thorougly test each of other
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413719#comment-13413719
]
Michael McCandless commented on LUCENE-3892:
No, for docIDs we store docID -
[
https://issues.apache.org/jira/browse/SOLR-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413717#comment-13413717
]
Mark Miller commented on SOLR-3259:
---
I've created SOLR-3619 for the 'example' rename.
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413715#comment-13413715
]
Mark Miller commented on SOLR-3619:
---
>From SOLR-3259
> Rename 'example'
Mark Miller created SOLR-3619:
-
Summary: Rename 'example' dir to 'server'
Key: SOLR-3619
URL: https://issues.apache.org/jira/browse/SOLR-3619
Project: Solr
Issue Type: Improvement
Rep
[
https://issues.apache.org/jira/browse/SOLR-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413714#comment-13413714
]
Mark Miller commented on SOLR-3259:
---
bq. Could we solve it by providing some number of st
Very cool!
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jul 13, 2012 at 8:58 AM, Uwe Schindler wrote:
> When investigation an high IOwait on my linux server, I wanted to find out
> which process is consuming so much IO, and in fact it was one of those
> hanging solr tests! It took som
[
https://issues.apache.org/jira/browse/SOLR-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-3617:
-
Assignee: Mark Miller
> Consider adding start scripts.
> --
>
>
[
https://issues.apache.org/jira/browse/SOLR-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413713#comment-13413713
]
Mark Miller commented on SOLR-3617:
---
bq. As fan of Ubuntu, please also add a upstart conf
[
https://issues.apache.org/jira/browse/SOLR-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413712#comment-13413712
]
Mark Miller commented on SOLR-3617:
---
So I guess some things to consider here...where do w
On Fri, Jul 13, 2012 at 5:27 AM, Jan Høydahl wrote:
>
> My opinion is that we should stay an agnostic web-app so the downstream
> consumers and end-users of Solr has a real choice. But at the same time
> strive to make the built-in Jetty server work as well as possible OOTB (start
> scripts etc
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413709#comment-13413709
]
Han Jiang commented on LUCENE-3892:
---
bq. We could in theory subtract 1 from all these d
[
https://issues.apache.org/jira/browse/LUCENE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413711#comment-13413711
]
David Smiley commented on LUCENE-4173:
--
Instead of this boolean flag on the strategy
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-4211:
---
Attachment: LUCENE-4211.patch
New patch, fixing AssertingTermsEnum to track initial
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4211:
Attachment: LUCENE-4211.patch
Attached patch with fix for highlighter.
I will continue testing, I
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413698#comment-13413698
]
Michael McCandless commented on LUCENE-3892:
bq. But why? Does lucene store f
[
https://issues.apache.org/jira/browse/LUCENE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4211:
Attachment: LUCENE-4211.patch
Latest patch: I fixed up all javadocs, and also setup AssertingCodec
When investigation an high IOwait on my linux server, I wanted to find out
which process is consuming so much IO, and in fact it was one of those
hanging solr tests! It took some time to find a good tool, but here is it:
IOTOP (http://guichaz.free.fr/iotop/) - looks like TOP, but shows input and
o
> Then we should see some OOM somewhere in a stack trace!
We should. I mean should have. I've written a simple test that OOMs
and it does show up:
test:
[mkdir] Created dir: c:\Work\lucene-solr\lucene\build\core\test
[junit4:junit4] says g'day! Master seed: D82ABE551D56D0E3
[junit4:junit4] Y
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-139:
--
Attachment: SOLR-139_createIfNotExist.patch
Per the discussion on the mailing list, here's a patch that c
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java7-64/399/
No tests ran.
Build Log:
[...truncated 225 lines...]
ERROR: Failed to archive artifacts: heapdumps/**
hudson.util.IOException2: Failed to copy
/var/lib/jenkins/workspace/Lucene-Solr-4.x-Linux-Java7-64/heapdumps/**
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java7-64/525/
No tests ran.
Build Log:
[...truncated 5 lines...]
FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException:
Connection reset
hudson.remoting.RequestAbortedException:
hudson.remoting.RequestAb
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413682#comment-13413682
]
Han Jiang commented on LUCENE-3892:
---
bq. Was the numBits==0 case for all 0s not all 1s?
It is hanging again! Same test same issue! Everybody should review his commits
from yesterday!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Beh
Then we should see some OOM somewhere in a stack trace!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of
> Dawid Weiss
> Sent: Friday, Jul
It is possible.
Dawid
On Fri, Jul 13, 2012 at 1:45 PM, Robert Muir wrote:
> Maybe thats the problem? That its logging too much and causing OOM?
> Just an idea.
>
> On Fri, Jul 13, 2012 at 6:36 AM, Dawid Weiss
> wrote:
>> http://ophelia.cs.put.poznan.pl/~dweiss/lucene/output.zip
>>
>> Uh, these
Maybe thats the problem? That its logging too much and causing OOM?
Just an idea.
On Fri, Jul 13, 2012 at 6:36 AM, Dawid Weiss
wrote:
> http://ophelia.cs.put.poznan.pl/~dweiss/lucene/output.zip
>
> Uh, these tests emit a lot of logs...
>
> Dawid
>
> On Fri, Jul 13, 2012 at 12:10 PM, Dawid Weiss
>
> This helps in timeouting the tests, but it does not fix the issue of some
> tests itself going amok and hanging! :-)
Oh, absolutely. I'm the infrastructure guy -- I want tests to run and
fail with as much background information as possible so that folks who
know the rest of the system can fix t
[
https://issues.apache.org/jira/browse/LUCENE-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413647#comment-13413647
]
Uwe Schindler commented on LUCENE-4206:
---
I just wanted to add my recent blog post o
[
https://issues.apache.org/jira/browse/LUCENE-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413645#comment-13413645
]
Uwe Schindler commented on LUCENE-4202:
---
I just wanted to add my recent blog post o
[
https://issues.apache.org/jira/browse/LUCENE-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413644#comment-13413644
]
Uwe Schindler commented on LUCENE-4199:
---
I just wanted to add my recent blog post o
http://ophelia.cs.put.poznan.pl/~dweiss/lucene/output.zip
Uh, these tests emit a lot of logs...
Dawid
On Fri, Jul 13, 2012 at 12:10 PM, Dawid Weiss
wrote:
> I'll post a full stderr log in a minute.
> D.
>
> On Fri, Jul 13, 2012 at 12:06 PM, Uwe Schindler wrote:
>> We are currently investigatin
Hi since a few runs, days some test produces on FreeBSD and Linux produce on
every run (successful or not) a heapdump. This is caused by the test setting
we use for debugging: -XX:+HeapDumpOnOutOfMemoryError; this does not happen
on Windows, because it does not set this parameter in the JVM.
Did a
I'll post a full stderr log in a minute.
D.
On Fri, Jul 13, 2012 at 12:06 PM, Uwe Schindler wrote:
> We are currently investigating another hang. The next run also hung, it seems
> that a commit last night made the distributed tests hang forver.
>
> Dawid was decoding the test runner files (JSON
We are currently investigating another hang. The next run also hung, it seems
that a commit last night made the distributed tests hang forver.
Dawid was decoding the test runner files (JSON), this is printed to stdout all
the time (at 0% CPU):
4476606 T886 C82 P42953 oasc.RecoveryStrategy.doRec
This is a spinoff discussion from
https://issues.apache.org/jira/browse/SOLR-3613
Solr has so far been a Java web-app which runs in any servlet container, and we
have let users decide which one to use. As an example for newbies to quickly
get running we've included the lightweight Jetty contain
[
https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-3377.
Resolution: Fixed
I fixed the issue with +,- and committed to trunk and 4x
http://svn.apache.org/vie
1 - 100 of 106 matches
Mail list logo