Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11736/
Java: 32bit/jdk1.9.0-ea-b34 -server -XX:+UseSerialGC (asserts: false)
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.cloud.MultiThreadedOCPTest
Error Message:
1 thread leaked from SUITE scope at
Look at the actual change in question,
It is not missing tests and cannot be tested.
It is a guard against jvm bugs like buggy G1GC collector.
On Sat, Dec 6, 2014 at 11:25 PM, Michael Wechner
michael.wech...@wyona.com wrote:
Hi
Yesterday morning I have noticed the following changes
-
Hi Robert
Thanks very much for your feedback. I guess you mean the following change:
git diff
1f69438a17a0ad33bb9c209113b0fe83fb68f860..5bb9e0aebe18a67e5e0e4698e0553d6824327495
lucene/core/src/java/org/apache/lucene/index/IndexWriter.java
-assert lastCommitChangeCount = changeCount:
[
https://issues.apache.org/jira/browse/LUCENE-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237110#comment-14237110
]
ASF subversion and git services commented on LUCENE-6005:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237114#comment-14237114
]
ASF subversion and git services commented on LUCENE-5987:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237119#comment-14237119
]
ASF subversion and git services commented on LUCENE-6005:
-
Commit
Did you read the issue at all?
You have to run the test thousands of times with a particular random
seed to have a chance of reproducing.
On Sun, Dec 7, 2014 at 5:19 AM, Michael Wechner
michael.wech...@wyona.com wrote:
Hi Robert
Thanks very much for your feedback. I guess you mean the
On Sun, Dec 7, 2014 at 5:19 AM, Michael Wechner
michael.wech...@wyona.com wrote:
About missing tests, I guess you experienced a buggy G1GC collector or
other JVM bugs and hence you
made this change, right? If so, I guess you will run the new code with
the existing buggy G1GC collector
and if
Michael,
I recall you’re working on building a test tool that sees changes and runs
applicable tests? If that’s the case, why would it matter if CHANGES.txt
gets updated? The vast majority of the time there is a reference to a JIRA
issue from the commit message, and most JIRA issues that have
You are both right :-)
I was modifying schema.xml in the distribution and wanted to know
whether we had any Solr tests that covered/tested those files to
ensure I did not break anything.
I did not find any specific to my - truly minor - changes (now in
SOLR-6826), so ended up running the full
Hi Michael,
Awesome to see you are still working on that tool. It's enough outside
of the box, I can see it can cause other people without context to
become confused. But I think we will learn something from it, whether
it will ultimately work perfectly or not.
On the specific question: I was
Am 07.12.14 um 14:22 schrieb Robert Muir:
Did you read the issue at all?
I assume you mean
https://issues.apache.org/jira/browse/LUCENE-6098
No, I did not, my bad, sorry for that.
You have to run the test thousands of times with a particular random
seed to have a chance of reproducing.
you
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2294/
1 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.handler.TestReplicationHandler
Error Message:
file handle leaks:
Am 07.12.14 um 14:31 schrieb Robert Muir:
On Sun, Dec 7, 2014 at 5:19 AM, Michael Wechner
michael.wech...@wyona.com wrote:
About missing tests, I guess you experienced a buggy G1GC collector or
other JVM bugs and hence you
made this change, right? If so, I guess you will run the new code with
Hi David
Am 07.12.14 um 14:52 schrieb david.w.smi...@gmail.com:
Michael,
I recall you’re working on building a test tool that sees changes and runs
applicable tests?
yes
If that’s the case, why would it matter if CHANGES.txt
gets updated?
I think in the long term it is not just about
Hi Alex
Am 07.12.14 um 14:59 schrieb Alexandre Rafalovitch:
Hi Michael,
Awesome to see you are still working on that tool. It's enough outside
of the box, I can see it can cause other people without context to
become confused. But I think we will learn something from it, whether
it will
[
https://issues.apache.org/jira/browse/SOLR-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237203#comment-14237203
]
Mark Miller commented on SOLR-6554:
---
I don't think we need to support live migrations
[
https://issues.apache.org/jira/browse/SOLR-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237204#comment-14237204
]
Mark Miller commented on SOLR-6554:
---
Bq. Why not in 6?
Supporting both over 5x will
Robert Muir created LUCENE-6100:
---
Summary: Further tuning of Lucene50Codec(BEST_COMPRESSION)
Key: LUCENE-6100
URL: https://issues.apache.org/jira/browse/LUCENE-6100
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-6100:
Attachment: LUCENE-6100.patch
Further tuning of Lucene50Codec(BEST_COMPRESSION)
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11738/
Java: 32bit/jdk1.9.0-ea-b34 -server -XX:+UseSerialGC (asserts: true)
1 tests failed.
FAILED: org.apache.solr.cloud.DeleteReplicaTest.testDistribSearch
Error Message:
Should have had a good message here
Stack Trace:
[
https://issues.apache.org/jira/browse/SOLR-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy Zhovtyuk updated SOLR-6019:
---
Attachment: SOLR-6019.patch
File should be available for viewing in admin UI, but should be
[
https://issues.apache.org/jira/browse/SOLR-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy Zhovtyuk updated SOLR-6016:
---
Attachment: SOLR-6016.patch
Updated to latest trunk. Removed whitespace changes.
Failure
Joel Bernstein created LUCENE-6101:
--
Summary: Allow the SlowCompositeReaderWrapper and MultiDocValues
to accept acceptableOverheadRatio for OrdinalMap
Key: LUCENE-6101
URL:
[
https://issues.apache.org/jira/browse/LUCENE-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated LUCENE-6101:
---
Attachment: lucene-6101.patch
Allow the SlowCompositeReaderWrapper and MultiDocValues to
[
https://issues.apache.org/jira/browse/LUCENE-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237279#comment-14237279
]
Robert Muir commented on LUCENE-6101:
-
This is essentially an implementation detail
Build: https://builds.apache.org/job/Lucene-Solr-Maven-5.x/780/
3 tests failed.
FAILED: org.apache.solr.hadoop.MorphlineBasicMiniMRTest.testPathParts
Error Message:
Test abandoned because suite timeout was reached.
Stack Trace:
java.lang.Exception: Test abandoned because suite timeout was
[
https://issues.apache.org/jira/browse/LUCENE-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237312#comment-14237312
]
Robert Muir commented on LUCENE-6097:
-
+1
do tests survive a moderate beasting?
I
[
https://issues.apache.org/jira/browse/LUCENE-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-5735:
-
Attachment: LUCENE-5735.patch
Here's the patch, with randomized testing verification of results.
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4372/
Java: 32bit/jdk1.7.0_67 -server -XX:+UseParallelGC (asserts: true)
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.testDistribSearch
Error Message:
There were too many update fails - we expect it can
[
https://issues.apache.org/jira/browse/SOLR-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-6787:
-
Description:
A special collection called .system needs to be created by the user to
store/manage blobs.
Ideally, I'd like to just tell a node to rejoin at head and have to do
nothing else.
The rejoin-at-head is an internal API which is used by other APIs (and not
exposed to others). So , in that way it is a ready-to-cook API and not a
ready-to-eat one. So, use it with caution.
The entity that
[
https://issues.apache.org/jira/browse/SOLR-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237482#comment-14237482
]
Shawn Heisey commented on SOLR-6787:
This sounds very cool.
I do have a couple of
David Smiley created SOLR-6827:
--
Summary: DateRangeField: support facet.range, exclusive range,
DateMath
Key: SOLR-6827
URL: https://issues.apache.org/jira/browse/SOLR-6827
Project: Solr
Issue
[
https://issues.apache.org/jira/browse/SOLR-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta updated SOLR-1632:
---
Attachment: SOLR-1632.patch
Updated patch with minor changes. I've also benchmarked this test on my
[
https://issues.apache.org/jira/browse/SOLR-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-6827:
---
Attachment: SOLR-6827.patch
Note: This patch depends on refactorings in the patch on LUCENE-5735 that
[
https://issues.apache.org/jira/browse/SOLR-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237515#comment-14237515
]
David Smiley commented on SOLR-6827:
In a separate issue, I'll add terms-enum style
37 matches
Mail list logo
