lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dawid Weiss <dawid.we...@cs.put.poznan.pl>
Subject Re: Intermittent testing errors in TestSystemPropertiesInvariantRule
Date Wed, 21 Mar 2012 21:12:08 GMT
This one is a larger report from Carrot2/head test (quick, hence so
many assumption-ignored tests):
http://goo.gl/ObzE8

Dawid


On Wed, Mar 21, 2012 at 10:04 PM, Erick Erickson
<erickerickson@gmail.com> wrote:
> Oh, my goodness, that will be sweet.
>
> And my problem is...my problem. Had ICUFoldingFilterFactory in my core
> schema.xml by mistake, had meant to take it out. So, of all things,
> ShowFileReqeustHandlerTest was failing..... because ICUFFF couldn't be
> found by the classloader.
>
> Thanks for cleaning stuff up, although I'm perfectly willing to live
> with it, I've just got to learn what's "real" and what's not
>
> Chris:
> Thanks.
>
> On Wed, Mar 21, 2012 at 4:37 PM, Dawid Weiss
> <dawid.weiss@cs.put.poznan.pl> wrote:
>>> "grep FAILED" on the test results? That found what's below, but is
>>> it sufficient to find them all?
>>
>> The definite answer is each suite's summary line -- number of
>> failures/ errors being non-zero. I will silence those framework tests
>> to make life simpler.
>>
>>> But I'd have gone ahead and checked it in based on not being able to fail
>>> anything found with "reproduce with", which is bad so I need to know
>>> the magic...
>>
>> As soon as we release 3.x I plan to merge in LUCENE-3808. It really
>> should make things simpler. Staszek's been working on a nice modern
>> html5 report; here's a peek at the recent build failure I got, for
>> example:
>>
>> http://ophelia.cs.put.poznan.pl/~dweiss/lucene/tests-report-core/
>>
>> The console output is also much, much cleaner as only those suites
>> that actually failed emit any output (verbose output is stored in
>> another file and error-only suites is yet another to speed up locating
>> the offender).
>>
>> All the above requires infrastructural changes that go beyond my
>> ability to integrate with 3.x at the moment; I can hardly keep up with
>> merging changes from the trunk.
>>
>> D.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message