[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793283#comment-13793283
]
ASF subversion and git services commented on LUCENE-5273:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793288#comment-13793288
]
Steve Rowe commented on LUCENE-5273:
[~markrmil...@gmail.com], do you want this on th
[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated LUCENE-5273:
---
Fix Version/s: 5.0
> Binary artifacts in Lucene and Solr convenience binary distributions
> accompa
[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793299#comment-13793299
]
Uwe Schindler edited comment on LUCENE-5273 at 10/12/13 8:31 AM:
--
[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793299#comment-13793299
]
Uwe Schindler commented on LUCENE-5273:
---
bq. Hmm, the Maven Ant Tasks install and d
[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-5273:
--
Attachment: LUCENE-5273-optimized.patch
Here the patch. ant generate-maven-articfatcs succeeds
[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793315#comment-13793315
]
Uwe Schindler commented on LUCENE-5273:
---
BTW: I was hoping this patch also prevent
[
https://issues.apache.org/jira/browse/LUCENE-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Areek Zillur updated LUCENE-5260:
-
Attachment: LUCENE-5260.patch
Thanks for the review, Michael! I fixed the UnsortedTermFreqIterat
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/7853/
Java: 64bit/jdk1.8.0-ea-b106 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
All tests passed
Build Log:
[...truncated 7572 lines...]
[junit4] JVM J1: stdout was not empty, see:
/mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Lin
Build: builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/63029/
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestSnapshotDeletionPolicy.testMultiThreadedSnapshotting
Error Message:
Stack Trace:
java.lang.NullPointerException
at
org.apache.lucene.index.SnapshotDele
Not good! I'll dig. We should hold 4.5.1...
Mike McCandless
http://blog.mikemccandless.com
On Sat, Oct 12, 2013 at 9:11 AM, wrote:
> Build: builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/63029/
>
> 1 tests failed.
> REGRESSION:
> org.apache.lucene.index.TestSnapshotDeletio
I'll dig ...
Mike McCandless
http://blog.mikemccandless.com
On Sat, Oct 12, 2013 at 1:34 AM, Policeman Jenkins Server
wrote:
> Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/7753/
> Java: 32bit/jdk1.6.0_45 -server -XX:+UseParallelGC
>
> 1 tests failed.
> REGRESSION:
> org.apache
Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/474/
1 tests failed.
REGRESSION:
org.apache.solr.spelling.SpellCheckCollatorTest.testEstimatedHitCounts
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
at org.apache.solr.So
On Oct 12, 2013, at 9:55 AM, Michael McCandless
wrote:
> Not good! I'll dig. We should hold 4.5.1...
I'm not in a major hurry - I figured we should at least give a few days to let
the back ports bake a bit and see if anything else critical comes up.
While it would certainly be easier for m
[
https://issues.apache.org/jira/browse/SOLR-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793453#comment-13793453
]
ASF subversion and git services commented on SOLR-5324:
---
Commit 15315
> From a practical perspective, I've setup the lucene/solr 4.5 branch tests to
> run on my full metal jenkins box, I've built test artifacts and uploaded and
> smoke tested them, and I've got my email signing tested and in working
> order. So hopefully it will be pretty quick and easy when we are r
[
https://issues.apache.org/jira/browse/SOLR-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4327:
--
Fix Version/s: 5.0
4.6
4.5.1
Assignee: Mark Miller
> Solr
I committed a fix; I caused this when I "fixed" LUCENE-5263.
Mike McCandless
http://blog.mikemccandless.com
On Sat, Oct 12, 2013 at 9:55 AM, Michael McCandless
wrote:
> I'll dig ...
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sat, Oct 12, 2013 at 1:34 AM, Policeman Jenkins
Can anyone reproduce this failure?
I tried beasting with 1.7.0_05 but no fails ...
Mike McCandless
http://blog.mikemccandless.com
On Sat, Oct 12, 2013 at 9:11 AM, wrote:
> Build: builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/63029/
>
> 1 tests failed.
> REGRESSION:
> org.a
[
https://issues.apache.org/jira/browse/SOLR-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4327:
--
Attachment: SOLR-4327.patch
> SolrJ code review indicates potential for leaked HttpClient connections
>
[
https://issues.apache.org/jira/browse/SOLR-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793471#comment-13793471
]
Mark Miller commented on SOLR-4327:
---
Thanks Karl - this one missed my radar. I'll commit
[
https://issues.apache.org/jira/browse/SOLR-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4327:
--
Attachment: SOLR-4327.patch
> SolrJ code review indicates potential for leaked HttpClient connections
>
[
https://issues.apache.org/jira/browse/SOLR-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793480#comment-13793480
]
ASF subversion and git services commented on SOLR-4327:
---
Commit 15315
Just the seed? or the master seed. if its a jvm bug we need the latter.
flonkings already discarded the console log so we lost that, unless
you still have it open in a browser or something?
On Sat, Oct 12, 2013 at 4:39 PM, Michael McCandless
wrote:
> Can anyone reproduce this failure?
>
> I trie
[
https://issues.apache.org/jira/browse/SOLR-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793481#comment-13793481
]
ASF subversion and git services commented on SOLR-4327:
---
Commit 15315
[
https://issues.apache.org/jira/browse/SOLR-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793486#comment-13793486
]
ASF subversion and git services commented on SOLR-4327:
---
Commit 15315
Sigh, I didn't try the master seed, and no, I have no browser window open.
Maybe we can get the master seed included in a single test failure "snippet"?
Mike McCandless
http://blog.mikemccandless.com
On Sat, Oct 12, 2013 at 5:28 PM, Robert Muir wrote:
> Just the seed? or the master seed. if i
[
https://issues.apache.org/jira/browse/LUCENE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793521#comment-13793521
]
Michael McCandless commented on LUCENE-5189:
The test case changes look good!
Or just configure flonkings to hold the logs longer. I know the
defaults are bad for this: but you can change it to keep them for e.g.
3 days or something so that the disk space usage is constant.
On Sat, Oct 12, 2013 at 6:50 PM, Michael McCandless
wrote:
> Sigh, I didn't try the master seed, and
[
https://issues.apache.org/jira/browse/SOLR-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey closed SOLR-5339.
--
Resolution: Invalid
You can manually specify what hostname or address will go into the cloud
configurat
[
https://issues.apache.org/jira/browse/SOLR-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4327.
---
Resolution: Fixed
Thanks again Karl!
> SolrJ code review indicates potential for leaked HttpClient co
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/996/
1 tests failed.
REGRESSION: org.apache.solr.cloud.SyncSliceTest.testDistribSearch
Error Message:
Test Setup Failure: shard1 should have just been set up to be inconsistent -
but it's still consistent. Leader:http://127.0.0.1:5638
The wiki and the ref guide both say that Solr's embedded zookeeper will
default to SolrPort+1001 ... but that would result in a typical port of
9984. All the examples show 9983. I also checked the source code
(SolrZkServer), and it does appear to actually use +1000.
I'm pretty sure that changing
[
https://issues.apache.org/jira/browse/LUCENE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793579#comment-13793579
]
Shai Erera commented on LUCENE-5189:
Thanks for the comments Mike, I fixed the code.
[
https://issues.apache.org/jira/browse/LUCENE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793580#comment-13793580
]
ASF subversion and git services commented on LUCENE-5189:
-
Commit
Shawn Heisey created SOLR-5341:
--
Summary: Output version number in logs
Key: SOLR-5341
URL: https://issues.apache.org/jira/browse/SOLR-5341
Project: Solr
Issue Type: Improvement
Affects Vers
Or just keep the failures forever if there's such an option? (and
discard successful builds after a given time window)?
Mike -- what did you mean by "Maybe we can get the master seed
included in a single test failure "snippet"?"?
Dawid
On Sun, Oct 13, 2013 at 1:56 AM, Robert Muir wrote:
> Or ju
keeping around 4 days of builds now at max 1000 builds
simon
On Sun, Oct 13, 2013 at 1:56 AM, Robert Muir wrote:
> Or just configure flonkings to hold the logs longer. I know the
> defaults are bad for this: but you can change it to keep them for e.g.
> 3 days or something so that the disk space
38 matches
Mail list logo
