I went ahead and pushed it to sonatype. A patch is attached to
kLUCENE-5283. Let me know if this helps anyhow.

Dawid

On Tue, Oct 15, 2013 at 8:07 PM, Dawid Weiss
<dawid.we...@cs.put.poznan.pl> wrote:
> Oh, stop moaning. Just be more careful about the filters when you type them ;)
>
> I've committed a fix; this will only work from module level -- like I
> said, it may be very tricky to aggregate this across modules.
>
> https://github.com/carrotsearch/randomizedtesting/commit/78f40f506f933a5ec8dad38e9505fbf2aa6f7974
>
> I'll make a release tomorrow and integrate it with Lucene/ Solr builds.
>
> Dawid
>
>
> On Tue, Oct 15, 2013 at 5:59 PM, Michael McCandless
> <luc...@mikemccandless.com> wrote:
>> On Tue, Oct 15, 2013 at 11:47 AM, Yonik Seeley <ysee...@gmail.com> wrote:
>>> On Mon, Oct 14, 2013 at 10:41 AM, Michael McCandless
>>> <luc...@mikemccandless.com> wrote:
>>>> This has actually bit me before too ...
>>>
>>> Me too.
>>> I'm never sure if I may have made a typo... the only way to be sure is
>>> to tee the output to a file and go back through and look for the test
>>> output.
>>> I've also run things in a loop for an hour before I realized that they
>>> were running slightly too fast.
>>>
>>> I guess one answer is for me to create my own test script (not just
>>> for running in a loop, but even running a test a single time) that
>>> ensures (via grep) that at least one test was run.
>>
>> The python runner takes a "-once" argument to run the test only once
>> ... it's sort of backwards, but I originally created this runner in
>> order to beast a single test across multiple JVMs ... so when I want
>> to run a single test I do this:
>>
>>   python repeatLuceneTest.py TestFoo.testBar -once -nolog
>>
>> (-nolog sends all output to the console)
>>
>> And it will (now!) fail if you have a typo in your test case ...
>>
>> But ... I don't think it sets the classpath to run Solr tests now ...
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>

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

Reply via email to