Re: River Board Report

Whoops, Dan seems to have come back in Nov of 2011. The last change was Patricia resigning in March of 2012. Greg. On Tue, 2013-05-07 at 23:50, Greg Trasuk wrote: > Having searched the archives of private@, I see that the last change to > the PMC was in May of 2012, when Dan rejoined. > > Greg

Re: River Board Report

Having searched the archives of private@, I see that the last change to the PMC was in May of 2012, when Dan rejoined. Greg. On Tue, 2013-05-07 at 05:33, Greg Trasuk wrote: > It's that time again... Any issues or additions to the following? I > need to submit it before tomorrow. > > Question t

Re: ServiceDiscoveryManager lookp specification

I agree, I think we need to review this TCK test against the specification. I suspect more than one person created this test, perhaps there was confusion; at some point the resolution was changed to seconds (before Apache River's time). This meant if insufficient ServiceItem's are found, lookup

Build failed in Jenkins: river-qa-refactor-arm #37

See Changes: [peter_firmstone] Ensured that Distributed object's are constructed using privileges equivalent to CodeSource(null, null), very minimal to avoid the ability to prevent remote processes from creating privileged objects

Jenkins build is back to normal : river-qa-refactor-jdk7 #70

See

Build failed in Jenkins: river-qa-refactoring #80

See Changes: [peter_firmstone] Add meaningful messages to PreferredClassLoader logging output. ServiceDiscoveryManager concurrency updates; utilises java.util.concurrent, final and volatile fields, safe publication and prevention

Re: ServiceDiscoveryManager lookp specification

Hi Peter: I'd certainly apply some tolerance band to the test result. Failing for 3 ms difference is unreasonable. I'd expect probably 50-100ms variance. The ms clock isn't assumed to be that accurate. Matter of fact, waiting for a task switch could cause at least that much variance. Cheers,

Re: ServiceDiscoveryManager lookp specification

On 7/05/2013 8:17 PM, Peter Firmstone wrote: This test smells broken? I modified the output to read in milliseconds. Relevant ServiceDiscoveryManager method under test: public ServiceItem[] lookup(ServiceTemplate tmpl, int minMatches,

Re: Build failed in Jenkins: river-qa-refactoring #79

Looks like Jenkins was unable to download proxy jar's from ClassServer. Seems like Jenkins is less reliable lately, OSX and ARM haven't been available for some time and we continue to have socket availability issues. I'm not sure if it's worth the effort to convert the qa suite to use dynamic

ServiceDiscoveryManager lookp specification

This test smells broken? I modified the output to read in milliseconds. Relevant ServiceDiscoveryManager method under test: public ServiceItem[] lookup(ServiceTemplate tmpl, int minMatches, int maxMatches,

River Board Report

It's that time again... Any issues or additions to the following? I need to submit it before tomorrow. Question to all - For the life of me I can't find an email with a record of our last new committer. I think it was Dennis, but I can't remember the date - anyone? Cheers, Greg. Apache River