river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricia Shanahan <p...@acm.org>
Subject Re: ServiceDiscoveryManager test coverage
Date Sun, 22 Aug 2010 01:54:06 GMT
I've checked out branches/2.1.2 and started a test, with 
servicediscovery added to its qa.run target. I'll let you know what happens.


On 8/21/2010 6:00 PM, Peter Firmstone wrote:
> I'm probably not going to find time to run the tests for about a week,
> however we should probably start back at the last release and confirm
> that runs as expected first.
> Peter Firmstone wrote:
>> I'm aware that some of the tests that aren't being run are known
>> failures due to the missing Kerberos Key Server and Squid Proxy
>> server. I had one zone set up on apache zones for the KDC, however I
>> haven't set that up. I'm not sure if the same zone can be used for the
>> Kerberos Key server and the Proxy, or if we need a new proxy server
>> zone too.
>> Patricia Shanahan wrote:
>>> On 8/21/2010 3:43 PM, Peter Firmstone wrote:
>>> ...
>>>> This is unfortunate, to solve it, I'll to have to go back in time &
>>>> find
>>>> out when these tests were passing, then figure out what change/s caused
>>>> the failures. It could be the reduced amount of synchronization time in
>>>> TaskManager, but I'm only guessing.
>>> ...
>>>> [java] # of tests started = 40
>>>> [java] # of tests completed = 40
>>>> [java] # of tests passed = 30
>>>> [java] # of tests failed = 10
>>> Presumably, the errors were (re)introduced after build.xml or
>>> something was changed to drop the servicediscovery tests. It may be
>>> easier to bound the time frame by looking for that change.
>>> Could you also do a review to find out whether there are any other
>>> tests that are not being run? It definitely needs to be done, and you
>>> are much more familiar with the test set-up than I am. If you don't
>>> have time, I'll try.
>>> Patricia

View raw message