Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux/291/
Java: 32bit/ibm-j9-jdk6
1 tests failed.
REGRESSION: org.apache.lucene.store.TestBufferedIndexInput.testSetBufferSize
Error Message:
Stack Trace:
java.lang.AssertionError
at
__randomizedtesting.SeedInfo.seed([3C1
See
Changes:
[sarowe] Add new test-framework dependencies introduced by Mark Miller's
r1370864 commit: javax.servlet:servlet-api; org.eclipse.jetty:jetty-servlet;
and org.eclipse.jetty:jetty-util (jetty-util was previously runtime scope, but
is now compile scope)
[hossman] remove broken @ret
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows/153/
Java: 32bit/jdk1.7.0_05 -server -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 20029 lines...]
javadocs-lint:
[...truncated 1675 lines...]
BUILD FAILED
C:\Jenkins\workspace\Lucene-Solr-4.x-Windows\build.xml:47
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows/157/
Java: 32bit/jdk1.7.0_05 -server -XX:+UseG1GC
All tests passed
Build Log:
[...truncated 19851 lines...]
javadocs-lint:
[...truncated 1669 lines...]
BUILD FAILED
C:\Jenkins\workspace\Lucene-Solr-trunk-Windows\build.xml:47
On Wed, Aug 8, 2012 at 11:43 PM, Chris Hostetter
wrote:
>
> Can you honestly say you think it makes sense that someone who types
> in...
>
> fly-fishing
>
> ...will get match on documents containing either "fly" or "fishing" using
> the example "text_general" fieldType?
>
Can you honestl
: Anyone who *wants* a phrase query can ask for one with double quotes.
: If you force this option on, users have no way to turn it off.
:
: I'm strongly opposed. I could care less about english.
Hold on a minute and think about what jack is pointing out here.
I can understand your argument aga
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows/152/
Java: 32bit/jdk1.7.0_05 -server -XX:+UseConcMarkSweepGC
All tests passed
Build Log:
[...truncated 20024 lines...]
javadocs-lint:
[...truncated 1676 lines...]
BUILD FAILED
C:\Jenkins\workspace\Lucene-Solr-4.x-Windows\build
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows/156/
Java: 64bit/jdk1.7.0_05 -XX:+UseG1GC
All tests passed
Build Log:
[...truncated 19862 lines...]
javadocs-lint:
[...truncated 1670 lines...]
BUILD FAILED
C:\Jenkins\workspace\Lucene-Solr-trunk-Windows\build.xml:47: The fo
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows/151/
Java: 32bit/jdk1.7.0_05 -server -XX:+UseConcMarkSweepGC
All tests passed
Build Log:
[...truncated 20020 lines...]
javadocs-lint:
[...truncated 1675 lines...]
BUILD FAILED
C:\Jenkins\workspace\Lucene-Solr-4.x-Windows\build
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows/155/
Java: 32bit/jdk1.7.0_05 -client -XX:+UseParallelGC
All tests passed
Build Log:
[...truncated 19858 lines...]
javadocs-lint:
[...truncated 1672 lines...]
BUILD FAILED
C:\Jenkins\workspace\Lucene-Solr-trunk-Windows\build.
See
Changes:
[Robert Muir] LUCENE-4297: BooleanScorer2 sometimes multiplies coord() twice
into the score
[Robert Muir] harden test against internet problems
[sarowe] fix doc bugs (thanks to Oren Bochman)
[Robert Muir] turn on nightly-smoke task
[Robert Muir] LUCENE-4295: add task to build a
Where are the actual relevance measurements showing degradation? For
every example you have, i can give you a counter-example, including
whole languages that flat out won't work at all.
Anyone who *wants* a phrase query can ask for one with double quotes.
If you force this option on, users have no
Digging through the Jira and revision history, I discovered that back at the
end of May 2011, a change was made to Solr that fairly significantly
degrades the OOTB behavior for Solr queries, namely for word-splitting of
terms with embedded punctuation, so that they end up, by default, doing the
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431511#comment-13431511
]
Michael McCandless commented on LUCENE-3892:
OK I'll merge & replace Block w/
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431506#comment-13431506
]
Adrien Grand commented on LUCENE-3892:
--
Sounds good. I think the only commits that h
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431504#comment-13431504
]
Michael McCandless commented on LUCENE-3892:
Yes I think we should do a hard
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431498#comment-13431498
]
Adrien Grand commented on LUCENE-3892:
--
Thanks Mike for your tests. Do you think {{B
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3892:
---
Attachment: LUCENE-3892-non-specialized.patch
I created a non-specialized (ie single
[
https://issues.apache.org/jira/browse/LUCENE-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431486#comment-13431486
]
Michael McCandless commented on LUCENE-4283:
Thanks Billy, patch looks good..
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431485#comment-13431485
]
Michael McCandless commented on LUCENE-3892:
I also see (smaller) gains with
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431433#comment-13431433
]
Uwe Schindler commented on LUCENE-3312:
---
bq. Some tests throw OutOfMemory errors (b
[
https://issues.apache.org/jira/browse/SOLR-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431425#comment-13431425
]
Hoss Man commented on SOLR-3722:
in addition to this, we should consider updating the compo
Hoss Man created SOLR-3722:
--
Summary: NPE from NamedList constructor if shard fails to return
auxilury data about all docs
Key: SOLR-3722
URL: https://issues.apache.org/jira/browse/SOLR-3722
Project: Solr
Thanks for the feedback. Let us know if you run into any more
issues/concerns.
Thanks,
Christopher
On Wed, Aug 8, 2012 at 1:33 PM, Granroth, Neal V. <
neal.granr...@thermofisher.com> wrote:
> Yes I pulled from the branch not the trunk. I apparently made the
> incorrect assumption that it would
Yes I pulled from the branch not the trunk. I apparently made the incorrect
assumption that it would be slightly more stable than the current
work-in-progress.
Thanks for the quick attention and clarifications. Especially for those that
rely upon the binary packages.
- Neal
-Original Me
Mark Miller introduced new dependencies from the solr test-framework on
jetty-servlet, jetty-util, and servlet-api - this caused compilation failures
under Maven, since these jars were not included in the compilation classpath:
--
[INFO] Compilation failure
/usr/home/hudson/hudson-slave/wor
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431346#comment-13431346
]
Nikola Tankovic edited comment on LUCENE-3312 at 8/8/12 8:14 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikola Tankovic updated LUCENE-3312:
Attachment: lucene-3312-patch-09.patch
Patch 09: small fix that fixes many Solr test, Solr
I use VS2010 and they opened fine for me to cut the pre-release nuget packages.
I'll try to take a in the next day or two to see if I can't move that back to a
VS2010 package.
I wouldn't have an issue with a VS2012 solution file - as long as it was in
VS2012 build folder, not the VS2010 folder;
thanks
guess that doesn't fail in core but does in test-framework? - search me.
On Aug 8, 2012, at 3:39 PM, hoss...@apache.org wrote:
> Author: hossman
> Date: Wed Aug 8 19:39:31 2012
> New Revision: 1370911
>
> URL: http://svn.apache.org/viewvc?rev=1370911&view=rev
> Log:
> remove broken @ret
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux/279/
Java: 32bit/jdk1.6.0_33 -client -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 10297 lines...]
javadocs-lint:
[...truncated 1696 lines...]
javadocs-lint:
[exec]
[exec] Crawl/parse...
[exec]
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows/152/
Java: 32bit/jdk1.6.0_33 -client -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 19037 lines...]
javadocs-lint:
[...truncated 1723 lines...]
javadocs-lint:
[exec]
[exec] Crawl/parse...
[exec]
It is configured in Jetty.
One more problem is that it happens so some times & some times it'll be fine
which is why it is being difficult for me to reproduce the scenario.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Ping-Request-Handler-Problem-tp3999880p337.h
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431324#comment-13431324
]
Adrien Grand edited comment on LUCENE-3892 at 8/8/12 7:38 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431324#comment-13431324
]
Adrien Grand commented on LUCENE-3892:
--
I did some changes to the {{BlockPacked}} co
[
https://issues.apache.org/jira/browse/LUCENE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431316#comment-13431316
]
Robert Muir commented on LUCENE-4219:
-
I tried to look into this, because its bad i t
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux/284/
Java: 32bit/jdk1.6.0_33 -server -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 10269 lines...]
javadocs-lint:
[...truncated 1691 lines...]
javadocs-lint:
[exec]
[exec] Crawl/parse...
[exec]
[
https://issues.apache.org/jira/browse/SOLR-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-3715:
---
Attachment: SOLR-3715.patch
Here's a patch that moves log record serialization outside of the synchron
I just pulled down the 3.0.3 branch from SVN and have encountered an initial
problem with the VisualStudio solution file Lucene.Net.Core.sln in the VS2010
folder.
This solution will not load in VS2010, Visual Studio complains that it was
created with a newer version.
Opening the solution file i
[
https://issues.apache.org/jira/browse/LUCENE-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431297#comment-13431297
]
Tom Burton-West commented on LUCENE-4286:
-
Thanks Robert for all your work on non
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux/278/
Java: 32bit/jdk1.6.0_33 -server -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 10387 lines...]
javadocs-lint:
[...truncated 1696 lines...]
javadocs-lint:
[exec]
[exec] Crawl/parse...
[exec]
Whether solr is configured in tomcat or jetty ?
I am trying replicated same thing in my PC ..
Let me get back to you once it is done .
Syed Abdul kather
send from Samsung S3
On Aug 8, 2012 11:54 PM, "vempap [via Lucene]" <
ml-node+s472066n319...@n3.nabble.com> wrote:
> Hello Syed,
>
> Thanks
Can you please paste you stack trace .. its easy for you to know reason.
Are you using solrcloud ?
Syed Abdul kather
send from Samsung S3
On Aug 8, 2012 9:55 PM, "vempap [via Lucene]" <
ml-node+s472066n399988...@n3.nabble.com> wrote:
> Hello,
>
> I've a problem with SOLR 4.0 Alpha ping request
Hello Syed,
Thanks for your reply. Unfortunately, there is not stack trace from Solr
side & I'm not using Solr Cloud.
It is sending an empty response back when I do a ping request. So, I'm not
able to figure out why it is sending an empty response without throwing an
exception - there is no exc
[
https://issues.apache.org/jira/browse/SOLR-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-3229.
Resolution: Fixed
Fix Version/s: 5.0
Committed revision 1370870. - trunk
Committed revision 1370871.
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/570/
No tests ran.
Build Log:
[...truncated 7976 lines...]
[INFO] Compiling 19 source files to
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-Maven-trunk/checkout/maven-build/solr/test-framework/target/classes
[INFO] -
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431117#comment-13431117
]
Han Jiang edited comment on LUCENE-3892 at 8/8/12 5:47 PM:
---
And
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431240#comment-13431240
]
Uwe Schindler commented on LUCENE-3312:
---
Hi Nikola,
next week is "pencils down", so
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/3033/
1 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.handler.TestReplicationHandler
Error Message:
ERROR: SolrIndexSearcher opens=76 closes=75
Stack Trace:
java.lang.AssertionError: ERROR: SolrIndexSearc
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431206#comment-13431206
]
Pascal Chollet commented on LUCENE-4297:
Thanks for fixing it so quickly!
[
https://issues.apache.org/jira/browse/SOLR-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431203#comment-13431203
]
Mark Miller commented on SOLR-3721:
---
Correct, only one recovery should run at a time. I'l
Hello,
I've a problem with SOLR 4.0 Alpha ping request handler. If there are many
cores & if I do start all the solr instances and they are up & running
successfully, when I do a create index it fails with logs saying that one of
the instances is down. I really donno why it is happening as start
[
https://issues.apache.org/jira/browse/SOLR-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431199#comment-13431199
]
Hoss Man commented on SOLR-3229:
bq. I use "doc-0" to make it compatible with single node m
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431193#comment-13431193
]
Robert Muir commented on LUCENE-3892:
-
{quote}
So ... most of the gains come from Blo
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3892:
---
Attachment: LUCENE-3892-bulkVInt.patch
I tested BulkVInt again, ie to decouple the c
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4297.
-
Resolution: Fixed
Thanks to Pascal for discovering this
> BooleanScorer2 someti
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4297:
Fix Version/s: (was: 3.6.1)
3.6.2
> BooleanScorer2 sometimes multiplies
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4297:
Fix Version/s: 3.6.1
4.0
5.0
> BooleanScorer2 sometimes
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431139#comment-13431139
]
Robert Muir commented on LUCENE-4297:
-
It is: basically the reason TestBoolean2.testR
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431137#comment-13431137
]
Uwe Schindler commented on LUCENE-4297:
---
Is BQ1 correct? Just to be sure!
+1 to bac
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4297:
Attachment: LUCENE-4297.patch
patch with improved testing: sometimes use a coord() like this in
l
Hi,
I'm also running Mac OS now (besides windows still ,-) and was able to build
& install PyLucene 3.6.0.2 on MacOS-X (10.7/intel/Python2.7) without any
problems - that's the good news.
However it was quite difficult for me to get the download files and
installation instructions:
Download
[
https://issues.apache.org/jira/browse/SOLR-3707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-3707:
--
Fix Version/s: 5.0
> Upgrade Solr to Tika 1.2
>
>
> Key: SO
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431125#comment-13431125
]
Robert Muir commented on LUCENE-4297:
-
Simple patch: remove the coord multiplication
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4297:
Attachment: LUCENE-4297.patch
> BooleanScorer2 sometimes multiplies coord() twice into the sco
[
https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431117#comment-13431117
]
Han Jiang commented on LUCENE-3892:
---
And result on skipMulitiplier, use current 8 as th
[
https://issues.apache.org/jira/browse/LUCENE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4297:
Attachment: LUCENE-4297_test.patch
here's a test. See e.g. ant test -Dtestcase=TestBoolean2
-Dte
Robert Muir created LUCENE-4297:
---
Summary: BooleanScorer2 sometimes multiplies coord() twice into
the score
Key: LUCENE-4297
URL: https://issues.apache.org/jira/browse/LUCENE-4297
Project: Lucene - Core
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows/147/
Java: 32bit/jdk1.7.0_05 -client -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 19855 lines...]
javadocs-lint:
[...truncated 1669 lines...]
BUILD FAILED
C:\Jenkins\workspace\Lucene-Solr-trunk-Windows\build.xm
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows/142/
Java: 32bit/jdk1.6.0_33 -client -XX:+UseConcMarkSweepGC
All tests passed
Build Log:
[...truncated 19168 lines...]
javadocs-lint:
[...truncated 1674 lines...]
BUILD FAILED
C:\Jenkins\workspace\Lucene-Solr-4.x-Windows\build
[
https://issues.apache.org/jira/browse/SOLR-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Steffensen updated SOLR-3721:
-
Environment: Using our own Solr release based on Apache revision 1355667
from 4.x branch. Our chan
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux/273/
Java: 32bit/ibm-j9-jdk7
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestDocumentsWriterStallControl.testSimpleStall
Error Message:
Left-over thread detected (and terminated): Thread[Thread-93,5,] (stack trace
[
https://issues.apache.org/jira/browse/LUCENE-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430958#comment-13430958
]
Han Jiang commented on LUCENE-4283:
---
Hmm, the improvement isn't that noisy
{noformat}
I can do that end of week when back from vacation!
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Tuesday, August 07, 2012 11:29 PM
> To: dev@lucene.ap
[
https://issues.apache.org/jira/browse/SOLR-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Steffensen updated SOLR-3721:
-
Attachment: recovery_start_finish.log
recovery_in_progress.png
> Multiple conc
Per Steffensen created SOLR-3721:
Summary: Multiple concurrent recoveries of same shard?
Key: SOLR-3721
URL: https://issues.apache.org/jira/browse/SOLR-3721
Project: Solr
Issue Type: Bug
76 matches
Mail list logo
