Can you post the full log or at least put it up on the web somewhere when you're done?
I don't see failures here and can't help to debug until I can see a full log of a run.... Ta, Dan. On 31 March 2013 16:46, Greg Trasuk <[email protected]> wrote: > > Peter: > > I've run the test suite on MacOSX, and got the failure on the > ExpirationNotifyTest. Personally, given that the test looks pretty > contrived, I wouldn't hold up the release basedn on this failure. > Nonetheless, later tonight I'll try to run the test again with some more > debug logging to see if I can understand the failure a little more. > > Cheers, > > Greg. > > On Fri, 2013-03-29 at 09:44, Peter Firmstone wrote: > > Links to builds with test failures: > > > > > https://builds.apache.org/view/M-R/view/River/job/river-qa-refactor-arm/28/artifact/qa/result/qaresults-arm-Linux-1.7.0_06.zip > > > https://builds.apache.org/view/M-R/view/River/job/river-qa-refactor-jdk7/48/artifact/trunk/qa/result/qaresults-amd64-Linux-1.7.0_04.zip > > > https://builds.apache.org/view/M-R/view/River/job/river-qa-refactoring/59/artifact/trunk/qa/result/qaresults-i386-Linux-1.6.0_27.zip > > > > Any assistance is appreciated, to run only the failing tests, set the > > run-test property in your build.properties, then execute ant qa.run-tests > > > > eg: > > > run.tests=com/sun/jini/test/spec/javaspace/conformance/ExpirationNotifyTest.td,\ > > > com/sun/jini/test/spec/javaspace/conformance/snapshot/SnapshotExpirationNotifyTest.td > > > > Regards, > > > > Peter. > > > > Peter wrote: > > > You can download the test results from jenkins (can email the link > later). > > > > > > To reproduce the failures, you'll need to run the tests multiple > times. Are you running the qa-refactoring build? > > > > > > I understand the importance of the serialisation compatibility issue. > > > > > > Can you update the poms in skunk/qa-refactoring? I've included the > logging fix. > > > > > > Regards, > > > > > > Peter. > > > > > > ----- Original message ----- > > > > > >> On Mar 28, 2013, at 631PM, Peter Firmstone wrote: > > >> > > >> > > >>> Dennis Reedy wrote: > > >>> > > >>>> Hi, > > >>>> > > >>>> Was wondering how we are doing with getting the next release out > the door? > > >>>> I'd like to suggest that we move on this as soon as possible If > there are > > >>>> issues that do come up with the release, we can always release > again. > > >>>> > > >>>> Regards > > >>>> > > >>>> Dennis > > >>>> > > >>>> > > >>> We can safely ignore the failing jrmp tests (caused by sockets that > haven't > > >>> been closed), there are some failing Outrigger Lease tests (on > Jenkins) that > > >>> prevented me from releasing before I went on holiday. When these > tests are > > >>> passing, I'll release. In the mean time, if someone wants to > assist, they'll > > >>> be warmly welcomed. > > >>> > > >> I have run the tests and cannot reproduce any failures. Can you be > more > > >> specific? Also realize that we have some serious show stoppers wrt > River and > > >> Java 7. I suggest we address the critical issues we have now in > production for > > >> many users and move forward with a release. > > >> > > >> Regards > > >> > > >> Dennis > > >> > > > > > > > > > > >
