Fixed it in SVN, and it passes.

On Sat, Feb 13, 2010 at 10:50 PM,  <psm...@aconex.com> wrote:
>
>
>
>
> On 14/02/2010, at 17:42, Ryan Rawson <ryano...@gmail.com> wrote:
>
>> Ok, I figured it out...
>>
>> The test doesn't run!  Here is the test report:
>> http://hudson.zones.apache.org/hudson/job/HBase-Patch/1108/testReport/
>>
>> Note no 'zookeeper' package...
>>
>> This is because the junit test runner only runs classes that start with
>> Test.
>>
>> I'll fix this particular one.
>>
>
> Ah!  Nice find. This is why I like Maven's structure; everything under
> src/main/test is considered a test without having to configure anything. If
> one doesn't want a test to run, don't put it there (or use annotations to
> mark it as failing of something)
>
>
>
>> -ryan
>>
>> On Sat, Feb 13, 2010 at 8:58 PM, Ryan Rawson <ryano...@gmail.com> wrote:
>>>
>>> I might draw your attention to src/test/hbase-site.xml... while it
>>> doesnt have 2000 in it, it might be the source of some of your
>>> issues...
>>>
>>> I know I ran into weird classpath issues on test runs in intellij vs
>>> ant...
>>>
>>> On Sat, Feb 13, 2010 at 7:26 PM, Paul Smith <psm...@aconex.com> wrote:
>>>>
>>>> On 14/02/2010, at 2:17 PM, Ryan Rawson wrote:
>>>>
>>>>> Ill help you later... I'm out and about but it looks like the test is
>>>>> stale
>>>>> since the new default for that value is indeed 3000. Probably can just
>>>>> change it to 3000 for now...
>>>>
>>>> ok, well that's good to know.  I guess I relied on the last 'hudson back
>>>> to normal' email, figuring the current trunk build is ok (or does that not
>>>> run from trunk?) and figured it was me.
>>>>
>>>> thanks for the fast response!
>>>>
>>>> Paul
>>>>
>>>>
>>>
>

Reply via email to