thanks steve!
On Wed, Aug 29, 2012 at 8:02 AM, Steven A Rowe wrote:
> Simon has granted me access on flonkings Jenkins, and I've set up the
> hugerriblific build failure regex in the notification email configuration for
> the jobs hosted there. - Steve
>
> -Original Message-
> From: Ste
Reproduces for me with:
> [junit4:junit4] 2> NOTE: reproduce with: ant test
> -Dtestcase=GroupFacetCollectorTest
> -Dtests.method=testMVGroupedFacetingWithDeletes -Dtests.seed=BF2B1FB32B155A3
> -Dtests.multiplier=3 -Dtests.slow=true -Dtests.locale=sk_SK
> -Dtests.timezone=America/Atikokan -
[
https://issues.apache.org/jira/browse/SOLR-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Steffensen updated SOLR-3765:
-
Description:
Dialog with myself from solr-users mailing list:
Per Steffensen skrev:
{quote}
Hi
[
https://issues.apache.org/jira/browse/SOLR-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Steffensen updated SOLR-3765:
-
Description:
Dialog with myself from solr-users mailing list:
Per Steffensen skrev:
{qoute}
Hi
Per Steffensen created SOLR-3765:
Summary: Wrong handling of documents with same id in cross
collection searches
Key: SOLR-3765
URL: https://issues.apache.org/jira/browse/SOLR-3765
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe resolved SOLR-2747.
---
Resolution: Fixed
Fix Version/s: (was: 4.1)
5.0
4.0
C
> [junit4:junit4] ERROR: JVM J0 ended with an exception, command line:
> /usr/local/openjdk7/jre/bin/java -XX:+UseG1GC -Dtests.prefix=tests -
I checked again, this is caused by two interfering issues --
1) BasicDistributedZk2Test.testDistribSearch hangs on socket read (I
posted a stack trace a w
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux/723/
Java: 32bit/jdk1.6.0_34 -client -XX:+UseConcMarkSweepGC
1 tests failed.
REGRESSION:
org.apache.lucene.search.grouping.GroupFacetCollectorTest.testMVGroupedFacetingWithDeletes
Error Message:
limit=1 actual=2
Stack Trace:
j
Simon has granted me access on flonkings Jenkins, and I've set up the
hugerriblific build failure regex in the notification email configuration for
the jobs hosted there. - Steve
-Original Message-
From: Steven A Rowe [mailto:sar...@syr.edu]
Sent: Saturday, August 25, 2012 8:13 PM
To: d
Build: https://builds.apache.org/job/Lucene-Solr-Tests-4.x-java7/366/
All tests passed
Build Log:
[...truncated 7606 lines...]
[junit4:junit4] ERROR: JVM J0 ended with an exception, command line:
/usr/local/openjdk7/jre/bin/java -XX:+UseG1GC -Dtests.prefix=tests
-Dtests.seed=597A59E4DFFC3345 -X
On Tue, Aug 28, 2012 at 10:06 PM, Chris Hostetter
wrote:
> On the Solr side of things, i think we should even want to consider
> automaticly running IndexUpgrader on startup if we detect that the
> Lucene3xCodec is in use to simplify things -- we can't even suggest running
> "optimize" as a quick/
On Tue, Aug 28, 2012 at 10:06 PM, Chris Hostetter
wrote:
>
> On the solr-user list, Dirk Högemann recently mentioned a problem he was
> seeing when he tried upgrading his existing solr setup from 3.x to 4.0-BETA.
> Specifically this exception getting logged...
>
> http://find.searchhub.org/documen
On the solr-user list, Dirk Högemann recently mentioned a problem he was
seeing when he tried upgrading his existing solr setup from 3.x to
4.0-BETA. Specifically this exception getting logged...
http://find.searchhub.org/document/cdb30099bfea30c6
auto commit error...:java.lang.UnsupportedO
[
https://issues.apache.org/jira/browse/SOLR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-3755:
---
Attachment: SOLR-3755.patch
Draft (unfinished) patch just to let people know where I'm going...
[
https://issues.apache.org/jira/browse/SOLR-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-3764.
Resolution: Cannot Reproduce
user error ... i had a typo in my path (big surprise, i know)
On Tue, Aug 28, 2012 at 5:42 PM, Chris Hostetter
wrote:
> If folks are concerned that certian tests fail to frequently to be
> considered "stable" and included in the main build, then let's:
>
> 1) slap a special "@UnstableTest" annotation on them
> 2) set up a new jenkins job that *only* runs
[
https://issues.apache.org/jira/browse/SOLR-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443691#comment-13443691
]
Hoss Man commented on SOLR-3764:
Steps to reproduce...
1) run the Solr 3.6.1 example and i
Hoss Man created SOLR-3764:
--
Summary: Upgrading to Solr 4 from Solr 3.x doesn't support "single
core" mode Solr Home dirs (ie: all 3.x examples)
Key: SOLR-3764
URL: https://issues.apache.org/jira/browse/SOLR-3764
[
https://issues.apache.org/jira/browse/LUCENE-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443679#comment-13443679
]
Adrien Grand commented on LUCENE-2810:
--
Oops, I didn't know of this issue when I ope
[
https://issues.apache.org/jira/browse/LUCENE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-4226:
-
Attachment: CompressionBenchmark.java
LUCENE-4226.patch
New patch as well as the
[
https://issues.apache.org/jira/browse/SOLR-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-3757.
Resolution: Fixed
Assignee: Hoss Man
Thanks for pointing that out Essoussi, I've tried to simplify th
THANK you Mr. Smiley!
I waited days for a response from someone. Thank you so much
Hi Dan,
That page is the in-progress documentation for this:
https://issues.apache.org/jira/browse/SOLR-3304 which hasn't been committed
and so it requires you check out Lucene/Solr and apply the patch. The cla
On August 12th, roughly the same day BasicDistributedZkTest#testDistribSearch
started failing regularly under the Maven builds, I reduced Solr log output
under the Maven builds, because Jenkins wasn't sending any notification emails
when the Maven builds failed, AFAICT because the voluminous Sol
[
https://issues.apache.org/jira/browse/LUCENE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-4336.
---
Resolution: Fixed
Fix Version/s: 4.0
5.0
Committed trunk revision:
[
https://issues.apache.org/jira/browse/LUCENE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443644#comment-13443644
]
Uwe Schindler edited comment on LUCENE-4336 at 8/29/12 10:21 AM:
--
[
https://issues.apache.org/jira/browse/LUCENE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4336:
--
Attachment: LUCENE-4336.patch
Here the patch. The javacc task is a little bit complicated (nee
[
https://issues.apache.org/jira/browse/LUCENE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned LUCENE-4336:
-
Assignee: Uwe Schindler
> javacc tasks should use ivy
> ---
: Off of the top of my head, the only thing I can figure is that the
: maven based tests are somehow getting the wrong schema sometimes.
: Maybe if there's some different with how solr homes are set between
: ant and maven?
that should be easy to sanity check right? add something like this into
On Fri, Aug 17, 2012 at 9:42 AM, Steven A Rowe wrote:
> Five out of the last seven builds have failed with this exact same ERROR.
>
> I can't reproduce on my Win7+Cygwin environment.
>
> Does anybody know what's happening here?
>
> If not, I'll ignore this test under Maven.
Pretty strange. I can
> 1) slap a special "@UnstableTest" annotation on them
> 2) set up a new jenkins job that *only* runs these @UnstableTest jobs
> 3) configure this new jenkins job to not send any email
>
> ...seems like that would satisfy everyone right?
I'm all for it. We can rename @BadApple to @Unstable and
: I didn't say that. I said the opposite - that having imperfect tests
: (or rather tests that cannot be fixed for whatever reason) discourages
: from looking at test failures and makes one just unsubscribe from the
: jenkins mails. If this is the case then yes, I think not having a test
: like th
[
https://issues.apache.org/jira/browse/LUCENE-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443560#comment-13443560
]
Steven Rowe commented on LUCENE-4335:
-
I'm not sure about Javacc, but I've seen JFlex
[
https://issues.apache.org/jira/browse/LUCENE-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss resolved LUCENE-4338.
-
Resolution: Fixed
Fix Version/s: 4.0
5.0
> Redirect java.io.tmpdir
[
https://issues.apache.org/jira/browse/LUCENE-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443536#comment-13443536
]
Dawid Weiss commented on LUCENE-4338:
-
Simple but does the job. I'm running tests rig
[
https://issues.apache.org/jira/browse/LUCENE-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443534#comment-13443534
]
Robert Muir commented on LUCENE-4338:
-
I don't know why I thought it would be trickie
[
https://issues.apache.org/jira/browse/LUCENE-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-4338:
Attachment: LUCENE-4338.patch
> Redirect java.io.tmpdir so that each JVM gets their own tmpdir
Dawid Weiss created LUCENE-4338:
---
Summary: Redirect java.io.tmpdir so that each JVM gets their own
tmpdir under a build/test
Key: LUCENE-4338
URL: https://issues.apache.org/jira/browse/LUCENE-4338
Proje
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443520#comment-13443520
]
Dawid Weiss commented on LUCENE-4332:
-
Sure, all I'm saying is that I know very littl
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443513#comment-13443513
]
Greg Bowyer commented on LUCENE-4332:
-
I can codify a security manager, they are some
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443512#comment-13443512
]
Uwe Schindler commented on LUCENE-4332:
---
You would need a simple Security manager t
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443509#comment-13443509
]
Robert Muir commented on LUCENE-4332:
-
I agree with you, i dont know anything about s
> Imperfect test coverage is better than no test coverage?
> Seems like we could simply disable all of our tests and then be happy
> because they will never fail ;-)
I didn't say that. I said the opposite - that having imperfect tests
(or rather tests that cannot be fixed for whatever reason) disc
On Tue, Aug 28, 2012 at 4:03 PM, Michael McCandless
wrote:
>> Another option is to redirect solr fails to a different mailing list
>> that only those that care about solr development can follow.
>
> I don't think splintering the dev community is healthy.
Well, it seems like some people would pref
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443501#comment-13443501
]
Dawid Weiss commented on LUCENE-4332:
-
bq. Well if its for test purposes only and not
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443497#comment-13443497
]
Dawid Weiss commented on LUCENE-4332:
-
As for generating a common seed for all runs -
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443491#comment-13443491
]
Robert Muir commented on LUCENE-4332:
-
{quote}
I didn't cater for the presence of a s
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443489#comment-13443489
]
Dawid Weiss commented on LUCENE-4332:
-
bq. OK, cool: its something we never did befor
Greg Bowyer created LUCENE-4337:
---
Summary: Create Java security manager for forcible asserting
behaviours in testing
Key: LUCENE-4337
URL: https://issues.apache.org/jira/browse/LUCENE-4337
Project: Luce
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443477#comment-13443477
]
Robert Muir commented on LUCENE-4332:
-
{quote}
They already do I think because tmpdir
On Tue, Aug 28, 2012 at 3:57 PM, Dawid Weiss
wrote:
> I don't agree with you here. I think having two or three failures
> daily from the same test (and typically with the same message) is far
> worse than not having it at all.
Imperfect test coverage is better than no test coverage?
Seems like we
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443471#comment-13443471
]
Dawid Weiss commented on LUCENE-4332:
-
bq. toFacyDawidWeissSeedFormat
That's just a
On Tue, Aug 28, 2012 at 3:04 PM, Yonik Seeley wrote:
> On Tue, Aug 28, 2012 at 2:43 PM, Dawid Weiss
> wrote:
>> 2) I think Solr emits a LOT of logging information to the console. I
>> don't know if all of it is really useful -- I doubt it, really.
>>
>> The solutions I see are simple -- disable t
[
https://issues.apache.org/jira/browse/LUCENE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443465#comment-13443465
]
Robert Muir commented on LUCENE-4336:
-
The javacc 5.0 is in maven repo (I upgraded to
[
https://issues.apache.org/jira/browse/LUCENE-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443464#comment-13443464
]
Robert Muir commented on LUCENE-4335:
-
{quote}
We should check what causes this.
{quo
> Another option is to redirect solr fails to a different mailing list
> that only those that care about solr development can follow.
I don't make a distinction between solr and lucene development, call me odd.
I did try to help with those few tests (and I fixed some others) but no luck.
> Tests
Actually, after discussing with Uwe on #lucene-dev IRC, I'm looking into
another mechanism to reduce the size of email messages: the Jenkins Email-Ext
plugin has a per-build-job configuration item named "Pre-send script" that
allows you to modify the MimeMessage object representing an email via
[
https://issues.apache.org/jira/browse/SOLR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440698#comment-13440698
]
Yonik Seeley edited comment on SOLR-3755 at 8/29/12 6:51 AM:
-
W
[
https://issues.apache.org/jira/browse/LUCENE-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443455#comment-13443455
]
Uwe Schindler commented on LUCENE-4335:
---
Thats a good idea, there is one problem wi
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443449#comment-13443449
]
Greg Bowyer edited comment on LUCENE-4332 at 8/29/12 6:48 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443449#comment-13443449
]
Greg Bowyer commented on LUCENE-4332:
-
Following up it turns out to be *very* simple
[
https://issues.apache.org/jira/browse/LUCENE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443448#comment-13443448
]
Uwe Schindler commented on LUCENE-4336:
---
+1, I can look into this! I hope this can
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443446#comment-13443446
]
Dilip Maddi commented on SOLR-139:
--
Christopher,
Here is how I am able to update a documen
Robert Muir created LUCENE-4336:
---
Summary: javacc tasks should use ivy
Key: LUCENE-4336
URL: https://issues.apache.org/jira/browse/LUCENE-4336
Project: Lucene - Core
Issue Type: Task
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443430#comment-13443430
]
Robert Muir commented on LUCENE-4332:
-
i think a security manager would be useful for
[
https://issues.apache.org/jira/browse/LUCENE-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443427#comment-13443427
]
Robert Muir commented on LUCENE-4335:
-
I think we should use replaceRegexp commands (
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443424#comment-13443424
]
Greg Bowyer commented on LUCENE-4332:
-
{quote}
Thats a cool idea also for our own tes
Michael McCandless created LUCENE-4335:
--
Summary: Builds should regenerate all generated sources
Key: LUCENE-4335
URL: https://issues.apache.org/jira/browse/LUCENE-4335
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/SOLR-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443409#comment-13443409
]
Greg Bowyer commented on SOLR-3763:
---
I guess my next step is to get caching working, I am
On Mon, Aug 20, 2012 at 2:22 PM, Dawid Weiss
wrote:
> Oh, one more thing -- if we suppress the console output we would
> absolutely have to keep (at jenkins) multiple tests-report.txt files
> because these always contain full output dumps (regardless of console
> settings). Otherwise we'd suppress
On Tue, Aug 28, 2012 at 2:43 PM, Dawid Weiss
wrote:
> 2) I think Solr emits a LOT of logging information to the console. I
> don't know if all of it is really useful -- I doubt it, really.
>
> The solutions I see are simple -- disable the tests that fail 3-5
> times and we still don't know what ca
[
https://issues.apache.org/jira/browse/LUCENE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443388#comment-13443388
]
Uwe Schindler commented on LUCENE-4322:
---
+1!! Smaller, smaller, smaller :-)
> Unfortunately, -Dtests.showOutput=never penalizes all tests that don't have
> megabytes of failure output because some do.
It doesn't penalize them, it says exactly what it does. A "full"
report is always written to disk, including all sysouts -- look at
tests-report.txt if I recall right.
> W
[
https://issues.apache.org/jira/browse/LUCENE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443343#comment-13443343
]
Dawid Weiss commented on LUCENE-4322:
-
Good idea, Andrien. More classes are definitel
Glad to help you!
- {@code ...} creates a ... environment, so ist formatted like
code.
- there is also {@literal ...} which makes the thing escaped, but plain text
(so its same font as remaining text)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u.
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443332#comment-13443332
]
Hoss Man commented on LUCENE-4332:
--
I had never heard of this technique until Greg menti
[
https://issues.apache.org/jira/browse/LUCENE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443313#comment-13443313
]
Michael McCandless commented on LUCENE-4322:
+1 for the first iteration.
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443304#comment-13443304
]
Greg Bowyer edited comment on LUCENE-4332 at 8/29/12 4:51 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443304#comment-13443304
]
Greg Bowyer commented on LUCENE-4332:
-
Wow lot of interest .
I will try to answe
[
https://issues.apache.org/jira/browse/LUCENE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443299#comment-13443299
]
Robert Muir commented on LUCENE-4324:
-
I think this is working pretty well now as far
[
https://issues.apache.org/jira/browse/LUCENE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443297#comment-13443297
]
Robert Muir commented on LUCENE-4322:
-
+1 for the first iteration.
>
[
https://issues.apache.org/jira/browse/LUCENE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443284#comment-13443284
]
Adrien Grand commented on LUCENE-4322:
--
bq. We could still shrink things further by
[
https://issues.apache.org/jira/browse/LUCENE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443267#comment-13443267
]
Michael McCandless commented on LUCENE-4322:
Patch looks good! That's a nice
[
https://issues.apache.org/jira/browse/LUCENE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-4322:
-
Attachment: LUCENE-4322.patch
Patch that tries to reduce the JAR size:
- unspecialized encode m
[
https://issues.apache.org/jira/browse/LUCENE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443246#comment-13443246
]
Adrien Grand commented on LUCENE-4322:
--
It looks like one of the reasons of the size
Aha! Most excellent. I'll switch to {@code ...}. Thanks for the pointer.
Mike McCandless
http://blog.mikemccandless.com
On Tue, Aug 28, 2012 at 10:35 AM, Uwe Schindler wrote:
> Hi Mike,
>
> The easier way (and also looks more code-style like):
> {@code Collection} - This escapes automaticall
Hi Dawid,
Unfortunately, -Dtests.showOutput=never penalizes all tests that don't have
megabytes of failure output because some do.
What do you think of adding an option to limit output size (e.g.
-Dtests.outputLimitKB=10), and truncating to that size if it's exceeded? If
you think this would
[
https://issues.apache.org/jira/browse/SOLR-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443202#comment-13443202
]
Yonik Seeley commented on SOLR-3763:
Interesting work Greg! A few points:
bq. Another
Hi Mike,
The easier way (and also looks more code-style like):
{@code Collection} - This escapes automatically and you can read it
better. It also added around!
See my recent additions to WeakIdentityMap :-)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
e
[
https://issues.apache.org/jira/browse/SOLR-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3088:
--
Fix Version/s: (was: 4.1)
5.0
4.0
> create shard placehold
[
https://issues.apache.org/jira/browse/SOLR-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-3088.
---
Resolution: Fixed
Assignee: Sami Siren
> create shard placeholders
> ---
[
https://issues.apache.org/jira/browse/SOLR-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443162#comment-13443162
]
Dawid Weiss commented on SOLR-3659:
---
Thanks Mark.
> non-reproducible fai
[
https://issues.apache.org/jira/browse/SOLR-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3347:
--
Fix Version/s: 5.0
> deleteByQuery failing with SolrCloud without _version_ in schema.xml
>
[
https://issues.apache.org/jira/browse/SOLR-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3465:
--
Fix Version/s: 5.0
4.0
> Replication Causes Two Searcher Warmups
> -
[
https://issues.apache.org/jira/browse/SOLR-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-3465:
-
Assignee: Mark Miller
> Replication Causes Two Searcher Warmups
> ---
[
https://issues.apache.org/jira/browse/SOLR-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443160#comment-13443160
]
Mark Miller commented on SOLR-3659:
---
This should be fixed now.
> non-rep
[
https://issues.apache.org/jira/browse/SOLR-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren updated SOLR-3507:
-
Attachment: SOLR-3507.patch
new patch updated to latest trunk with cleanups.
> Refactor p
[
https://issues.apache.org/jira/browse/LUCENE-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4334.
-
Resolution: Fixed
Fix Version/s: 4.0
5.0
seemed straightforward to me.
Robert Muir created LUCENE-4334:
---
Summary: remove unnecessary ant-junit dependency
Key: LUCENE-4334
URL: https://issues.apache.org/jira/browse/LUCENE-4334
Project: Lucene - Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4334:
Attachment: LUCENE-4334.patch
> remove unnecessary ant-junit dependency
>
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443081#comment-13443081
]
Uwe Schindler commented on LUCENE-4332:
---
bq. I also agree tests should somehow be r
1 - 100 of 114 matches
Mail list logo
