Re: Development Progress update.
I'm headed back to the UK so can test OS X in a couple of days if that's still useful... On 7 March 2013 05:25, Peter Firmstone wrote: > There are issues with some builds on Hudson, preventing test execution. > > Windows: a file can't be deleted in preparation for checkout, preventing > build from executing. > Solaris: BindException socket in use causes numerous test failures > FreeBSD: BindException socket in use, prevents build from executing. > OSX: offline. > > Apart from that, the tests are all passing on my Window's PC, Ubuntu x64 and > ARM. > > I need people who can volunteer to run QA tests! > > I wasn't attempting to improve performance, recent bug fixes have resulted > in the qa suite now finishing one hour earlier, which is a 6% performance > increase. > > Apart from fixing test failures, I've also used FindBugs to fix: > >* Javaspaces Outrigger: 13 multithreaded correctness bugs. >* Jini Platform: 5 inconsistent synchronization bugs. >* Jsk lib: 12 multithreaded correctness bugs. >* qa test suite: 20 multithreaded correctness bugs. > > Now's the time to checkout and run qa tests, then lets kick out a release. > > https://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk > > or > > http://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk > > Regards, > > Peter.
Re: Development Progress update.
Yes definitely, the more testing before release the better. Are you able to run the jtreg tests as well? They've only been tested on Solaris 10 sparc, I'm not aware of anyone else running jtreg tests for some time. Dan Creswell wrote: I'm headed back to the UK so can test OS X in a couple of days if that's still useful... On 7 March 2013 05:25, Peter Firmstone wrote: There are issues with some builds on Hudson, preventing test execution. Windows: a file can't be deleted in preparation for checkout, preventing build from executing. Solaris: BindException socket in use causes numerous test failures FreeBSD: BindException socket in use, prevents build from executing. OSX: offline. Apart from that, the tests are all passing on my Window's PC, Ubuntu x64 and ARM. I need people who can volunteer to run QA tests! I wasn't attempting to improve performance, recent bug fixes have resulted in the qa suite now finishing one hour earlier, which is a 6% performance increase. Apart from fixing test failures, I've also used FindBugs to fix: * Javaspaces Outrigger: 13 multithreaded correctness bugs. * Jini Platform: 5 inconsistent synchronization bugs. * Jsk lib: 12 multithreaded correctness bugs. * qa test suite: 20 multithreaded correctness bugs. Now's the time to checkout and run qa tests, then lets kick out a release. https://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk or http://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk Regards, Peter.
Re: Development Progress update.
Recent test failures: Solaris sparc: com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td Ubuntu JDK7 com/sun/jini/test/impl/outrigger/leasing/UseTxnMgrSpaceLeaseTestRenewCancel.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest2.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest3.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest4.td com/sun/jini/test/impl/outrigger/transaction/BlockingOnDeadTransactionTest.td Ubuntu Arm embedded com/sun/jini/test/impl/outrigger/leasing/UseNotifyLeaseTestRenewShutdown.td Ubuntu jdk6 com/sun/jini/test/spec/javaspace/conformance/ExpirationNotifyTest.td There are some remaining issues relating to unsafe publication, identified by find bugs (calling Thread.start() during construction), I'll fix these during the week, the failed jrmpexporter tests simply seem to be tests starting before previous tests sockets have been released by the OS. The remaining issues appear to be JavaSpace related. Regards, Peter. Dan Creswell wrote: I'm headed back to the UK so can test OS X in a couple of days if that's still useful... On 7 March 2013 05:25, Peter Firmstone wrote: There are issues with some builds on Hudson, preventing test execution. Windows: a file can't be deleted in preparation for checkout, preventing build from executing. Solaris: BindException socket in use causes numerous test failures FreeBSD: BindException socket in use, prevents build from executing. OSX: offline. Apart from that, the tests are all passing on my Window's PC, Ubuntu x64 and ARM. I need people who can volunteer to run QA tests! I wasn't attempting to improve performance, recent bug fixes have resulted in the qa suite now finishing one hour earlier, which is a 6% performance increase. Apart from fixing test failures, I've also used FindBugs to fix: * Javaspaces Outrigger: 13 multithreaded correctness bugs. * Jini Platform: 5 inconsistent synchronization bugs. * Jsk lib: 12 multithreaded correctness bugs. * qa test suite: 20 multithreaded correctness bugs. Now's the time to checkout and run qa tests, then lets kick out a release. https://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk or http://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk Regards, Peter.
Re: Development Progress update.
How do I run 'em? (I know about jtreg itself, just want the appropriate ant/command-line incantations to save me time). On 8 March 2013 22:32, Peter Firmstone wrote: > Yes definitely, the more testing before release the better. > > Are you able to run the jtreg tests as well? They've only been tested on > Solaris 10 sparc, I'm not aware of anyone else running jtreg tests for some > time. > > > Dan Creswell wrote: >> >> I'm headed back to the UK so can test OS X in a couple of days if >> that's still useful... >> >> On 7 March 2013 05:25, Peter Firmstone wrote: >> >>> >>> There are issues with some builds on Hudson, preventing test execution. >>> >>> Windows: a file can't be deleted in preparation for checkout, preventing >>> build from executing. >>> Solaris: BindException socket in use causes numerous test failures >>> FreeBSD: BindException socket in use, prevents build from executing. >>> OSX: offline. >>> >>> Apart from that, the tests are all passing on my Window's PC, Ubuntu x64 >>> and >>> ARM. >>> >>> I need people who can volunteer to run QA tests! >>> >>> I wasn't attempting to improve performance, recent bug fixes have >>> resulted >>> in the qa suite now finishing one hour earlier, which is a 6% performance >>> increase. >>> >>> Apart from fixing test failures, I've also used FindBugs to fix: >>> >>>* Javaspaces Outrigger: 13 multithreaded correctness bugs. >>>* Jini Platform: 5 inconsistent synchronization bugs. >>>* Jsk lib: 12 multithreaded correctness bugs. >>>* qa test suite: 20 multithreaded correctness bugs. >>> >>> Now's the time to checkout and run qa tests, then lets kick out a >>> release. >>> >>> https://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk >>> >>> or >>> >>> http://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk >>> >>> Regards, >>> >>> Peter. >>> >> >> >> > >
Re: Development Progress update.
$ cd qa $ ant jtreg If something goes wrong: $ ant jtreg-teardown to move files back. Cheers, Peter. Dan Creswell wrote: How do I run 'em? (I know about jtreg itself, just want the appropriate ant/command-line incantations to save me time). On 8 March 2013 22:32, Peter Firmstone wrote: Yes definitely, the more testing before release the better. Are you able to run the jtreg tests as well? They've only been tested on Solaris 10 sparc, I'm not aware of anyone else running jtreg tests for some time. Dan Creswell wrote: I'm headed back to the UK so can test OS X in a couple of days if that's still useful... On 7 March 2013 05:25, Peter Firmstone wrote: There are issues with some builds on Hudson, preventing test execution. Windows: a file can't be deleted in preparation for checkout, preventing build from executing. Solaris: BindException socket in use causes numerous test failures FreeBSD: BindException socket in use, prevents build from executing. OSX: offline. Apart from that, the tests are all passing on my Window's PC, Ubuntu x64 and ARM. I need people who can volunteer to run QA tests! I wasn't attempting to improve performance, recent bug fixes have resulted in the qa suite now finishing one hour earlier, which is a 6% performance increase. Apart from fixing test failures, I've also used FindBugs to fix: * Javaspaces Outrigger: 13 multithreaded correctness bugs. * Jini Platform: 5 inconsistent synchronization bugs. * Jsk lib: 12 multithreaded correctness bugs. * qa test suite: 20 multithreaded correctness bugs. Now's the time to checkout and run qa tests, then lets kick out a release. https://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk or http://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk Regards, Peter.
Re: Development Progress update.
I ran: ant qa.run [java] - [java] GENERAL HARNESS CONFIGURATION INFORMATION: [java] [java]Date started: [java] Sat Mar 09 08:19:09 EST 2013 [java]Installation directory of the JSK: [java] com.sun.jini.jsk.home=/Users/dreedy/dev/src/projects/river/qa-trunk [java]Installation directory of the harness: [java] com.sun.jini.qa.home=/Users/dreedy/dev/src/projects/river/qa-trunk/qa [java]Categories being tested: [java] categories=id loader policyprovider locatordiscovery activation config discoverymanager joinmanager url iiop jrmp reliability thread renewalmanager constraint export lookupdiscovery servicediscovery io security lookupservice renewalservice eventmailbox jeri start discoveryservice discoveryproviders javaspace txnmanager [java] - [java] ENVIRONMENT PROPERTIES: [java] [java]JVM information: [java] Java HotSpot(TM) 64-Bit Server VM, 23.7-b01, 64 bit VM mode [java] Oracle Corporation [java]OS information: [java] Mac OS X, 10.7.5, x86_64 [java] [java] [java] # of tests started = 1412 [java] # of tests completed = 1412 [java] # of tests skipped = 46 [java] # of tests passed= 1412 [java] # of tests failed= 0 [java] [java] - [java] [java]Date finished: [java] Sun Mar 10 00:45:27 EST 2013 [java]Time elapsed: [java] 59178 seconds On Mar 9, 2013, at 840PM, Peter Firmstone wrote: > Recent test failures: > > Solaris sparc: > > com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td > > Ubuntu JDK7 > > > com/sun/jini/test/impl/outrigger/leasing/UseTxnMgrSpaceLeaseTestRenewCancel.td > com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest2.td > com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest3.td > com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest4.td > > com/sun/jini/test/impl/outrigger/transaction/BlockingOnDeadTransactionTest.td > > Ubuntu Arm embedded > > com/sun/jini/test/impl/outrigger/leasing/UseNotifyLeaseTestRenewShutdown.td > > Ubuntu jdk6 > > com/sun/jini/test/spec/javaspace/conformance/ExpirationNotifyTest.td > > > There are some remaining issues relating to unsafe publication, identified by > find bugs (calling Thread.start() during construction), I'll fix these during > the week, the failed jrmpexporter tests simply seem to be tests starting > before previous tests sockets have been released by the OS. > > The remaining issues appear to be JavaSpace related. > > Regards, > > Peter. > > Dan Creswell wrote: >> I'm headed back to the UK so can test OS X in a couple of days if >> that's still useful... >> >> On 7 March 2013 05:25, Peter Firmstone wrote: >> >>> There are issues with some builds on Hudson, preventing test execution. >>> >>> Windows: a file can't be deleted in preparation for checkout, preventing >>> build from executing. >>> Solaris: BindException socket in use causes numerous test failures >>> FreeBSD: BindException socket in use, prevents build from executing. >>> OSX: offline. >>> >>> Apart from that, the tests are all passing on my Window's PC, Ubuntu x64 and >>> ARM. >>> >>> I need people who can volunteer to run QA tests! >>> >>> I wasn't attempting to improve performance, recent bug fixes have resulted >>> in the qa suite now finishing one hour earlier, which is a 6% performance >>> increase. >>> >>> Apart from fixing test failures, I've also used FindBugs to fix: >>> >>> * Javaspaces Outrigger: 13 multithreaded correctness bugs. >>> * Jini Platform: 5 inconsistent synchronization bugs. >>> * Jsk lib: 12 multithreaded correctness bugs. >>> * qa test suite: 20 multithreaded correctness bugs. >>> >>> Now's the time to checkout and run qa tests, then lets kick out a release. >>> >>> https://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk >>> >>> or >>> >>> http://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk >>> >>> Regards, >>> >>> Peter. >>> >> >> >
Re: Development Progress update.
I'm currently running this and jtreg, I'll report back when it's done. JDK 7 on OS X 10.8.2... On 10 March 2013 13:17, Dennis Reedy wrote: > I ran: > > ant qa.run > > [java] - > [java] GENERAL HARNESS CONFIGURATION INFORMATION: > [java] > [java]Date started: > [java] Sat Mar 09 08:19:09 EST 2013 > [java]Installation directory of the JSK: > [java] > com.sun.jini.jsk.home=/Users/dreedy/dev/src/projects/river/qa-trunk > [java]Installation directory of the harness: > [java] > com.sun.jini.qa.home=/Users/dreedy/dev/src/projects/river/qa-trunk/qa > [java]Categories being tested: > [java] categories=id loader policyprovider locatordiscovery activation > config discoverymanager joinmanager url iiop jrmp reliability thread > renewalmanager constraint export lookupdiscovery servicediscovery io security > lookupservice renewalservice eventmailbox jeri start discoveryservice > discoveryproviders javaspace txnmanager > [java] - > [java] ENVIRONMENT PROPERTIES: > [java] > [java]JVM information: > [java] Java HotSpot(TM) 64-Bit Server VM, 23.7-b01, 64 bit VM mode > [java] Oracle Corporation > [java]OS information: > [java] Mac OS X, 10.7.5, x86_64 > [java] > > > > [java] > [java] # of tests started = 1412 > [java] # of tests completed = 1412 > [java] # of tests skipped = 46 > [java] # of tests passed= 1412 > [java] # of tests failed= 0 > [java] > [java] - > [java] > [java]Date finished: > [java] Sun Mar 10 00:45:27 EST 2013 > [java]Time elapsed: > [java] 59178 seconds > > > On Mar 9, 2013, at 840PM, Peter Firmstone wrote: > >> Recent test failures: >> >> Solaris sparc: >> >> com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td >> >> Ubuntu JDK7 >> >> >> com/sun/jini/test/impl/outrigger/leasing/UseTxnMgrSpaceLeaseTestRenewCancel.td >> com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest2.td >> com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest3.td >> com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest4.td >> >> com/sun/jini/test/impl/outrigger/transaction/BlockingOnDeadTransactionTest.td >> >> Ubuntu Arm embedded >> >> com/sun/jini/test/impl/outrigger/leasing/UseNotifyLeaseTestRenewShutdown.td >> >> Ubuntu jdk6 >> >> com/sun/jini/test/spec/javaspace/conformance/ExpirationNotifyTest.td >> >> >> There are some remaining issues relating to unsafe publication, identified >> by find bugs (calling Thread.start() during construction), I'll fix these >> during the week, the failed jrmpexporter tests simply seem to be tests >> starting before previous tests sockets have been released by the OS. >> >> The remaining issues appear to be JavaSpace related. >> >> Regards, >> >> Peter. >> >> Dan Creswell wrote: >>> I'm headed back to the UK so can test OS X in a couple of days if >>> that's still useful... >>> >>> On 7 March 2013 05:25, Peter Firmstone wrote: >>> There are issues with some builds on Hudson, preventing test execution. Windows: a file can't be deleted in preparation for checkout, preventing build from executing. Solaris: BindException socket in use causes numerous test failures FreeBSD: BindException socket in use, prevents build from executing. OSX: offline. Apart from that, the tests are all passing on my Window's PC, Ubuntu x64 and ARM. I need people who can volunteer to run QA tests! I wasn't attempting to improve performance, recent bug fixes have resulted in the qa suite now finishing one hour earlier, which is a 6% performance increase. Apart from fixing test failures, I've also used FindBugs to fix: * Javaspaces Outrigger: 13 multithreaded correctness bugs. * Jini Platform: 5 inconsistent synchronization bugs. * Jsk lib: 12 multithreaded correctness bugs. * qa test suite: 20 multithreaded correctness bugs. Now's the time to checkout and run qa tests, then lets kick out a release. https://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk or http://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk Regards, Peter. >>> >>> >> >
Re: Development Progress update.
1412 passed, 46 skipped, 0 failures in about 58000 seconds. On 10 March 2013 13:26, Dan Creswell wrote: > I'm currently running this and jtreg, I'll report back when it's done. > > JDK 7 on OS X 10.8.2... > > > On 10 March 2013 13:17, Dennis Reedy wrote: >> I ran: >> >> ant qa.run >> >> [java] - >> [java] GENERAL HARNESS CONFIGURATION INFORMATION: >> [java] >> [java]Date started: >> [java] Sat Mar 09 08:19:09 EST 2013 >> [java]Installation directory of the JSK: >> [java] >> com.sun.jini.jsk.home=/Users/dreedy/dev/src/projects/river/qa-trunk >> [java]Installation directory of the harness: >> [java] >> com.sun.jini.qa.home=/Users/dreedy/dev/src/projects/river/qa-trunk/qa >> [java]Categories being tested: >> [java] categories=id loader policyprovider locatordiscovery activation >> config discoverymanager joinmanager url iiop jrmp reliability thread >> renewalmanager constraint export lookupdiscovery servicediscovery io >> security lookupservice renewalservice eventmailbox jeri start >> discoveryservice discoveryproviders javaspace txnmanager >> [java] - >> [java] ENVIRONMENT PROPERTIES: >> [java] >> [java]JVM information: >> [java] Java HotSpot(TM) 64-Bit Server VM, 23.7-b01, 64 bit VM mode >> [java] Oracle Corporation >> [java]OS information: >> [java] Mac OS X, 10.7.5, x86_64 >> [java] >> >> >> >> [java] >> [java] # of tests started = 1412 >> [java] # of tests completed = 1412 >> [java] # of tests skipped = 46 >> [java] # of tests passed= 1412 >> [java] # of tests failed= 0 >> [java] >> [java] - >> [java] >> [java]Date finished: >> [java] Sun Mar 10 00:45:27 EST 2013 >> [java]Time elapsed: >> [java] 59178 seconds >> >> >> On Mar 9, 2013, at 840PM, Peter Firmstone wrote: >> >>> Recent test failures: >>> >>> Solaris sparc: >>> >>> com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td >>> >>> Ubuntu JDK7 >>> >>> >>> com/sun/jini/test/impl/outrigger/leasing/UseTxnMgrSpaceLeaseTestRenewCancel.td >>> com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest2.td >>> com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest3.td >>> com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest4.td >>> >>> com/sun/jini/test/impl/outrigger/transaction/BlockingOnDeadTransactionTest.td >>> >>> Ubuntu Arm embedded >>> >>> >>> com/sun/jini/test/impl/outrigger/leasing/UseNotifyLeaseTestRenewShutdown.td >>> >>> Ubuntu jdk6 >>> >>> com/sun/jini/test/spec/javaspace/conformance/ExpirationNotifyTest.td >>> >>> >>> There are some remaining issues relating to unsafe publication, identified >>> by find bugs (calling Thread.start() during construction), I'll fix these >>> during the week, the failed jrmpexporter tests simply seem to be tests >>> starting before previous tests sockets have been released by the OS. >>> >>> The remaining issues appear to be JavaSpace related. >>> >>> Regards, >>> >>> Peter. >>> >>> Dan Creswell wrote: I'm headed back to the UK so can test OS X in a couple of days if that's still useful... On 7 March 2013 05:25, Peter Firmstone wrote: > There are issues with some builds on Hudson, preventing test execution. > > Windows: a file can't be deleted in preparation for checkout, preventing > build from executing. > Solaris: BindException socket in use causes numerous test failures > FreeBSD: BindException socket in use, prevents build from executing. > OSX: offline. > > Apart from that, the tests are all passing on my Window's PC, Ubuntu x64 > and > ARM. > > I need people who can volunteer to run QA tests! > > I wasn't attempting to improve performance, recent bug fixes have resulted > in the qa suite now finishing one hour earlier, which is a 6% performance > increase. > > Apart from fixing test failures, I've also used FindBugs to fix: > > * Javaspaces Outrigger: 13 multithreaded correctness bugs. > * Jini Platform: 5 inconsistent synchronization bugs. > * Jsk lib: 12 multithreaded correctness bugs. > * qa test suite: 20 multithreaded correctness bugs. > > Now's the time to checkout and run qa tests, then lets kick out a release. > > https://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk > > or > > http://svn.apache.org/repos/asf/river/jtsk/skunk/qa_refactor/trunk > > Regards, > > Peter. > >>> >>
Re: Development Progress update.
Cool, Thanks Dennis, Dan & Bryan, we're getting there! Bryan experienced two test failures on OSX: com/sun/jini/test/impl/start/CodebaseTest.td caused by: [java] CodebaseTest.run FINE: expected codebase for test service 1 proxy: http://Bryan-Thompson-MacBook-Air.local:9082/qa1-start-testservice1-dl.jar http://Bryan-Thompson-MacBook-Air.local:9082/qa1-start-testservice-common-dl.jar [java] CodebaseTest.run FINE: actual codebase for test service 1 proxy: http://bryan-thompson-macbook-air.local:9082/qa1-start-testservice1-dl.jar http://bryan-thompson-macbook-air.local:9082/qa1-start-testservice-common-dl.jar I've fixed it locally so both codebase strings are normalised, I'll upload the fix soon. The other: com/sun/jini/test/spec/javaspace/conformance/snapshot/SnapshotExpirationNotifyTest.td [java] Test Failed: Test Failed: com.sun.jini.qa.harness.TestException: Not all listeners've got expected number of events. I'm hoping that this is caused by the following bug I've discovered in com.sun.jini.jeri.internal.mux.StreamConnectionIO The LinkedList sendQueue access is synchronized with Mux.muxLock, unfortunately sendQueue's reference was copied to an instance variable and allowed to escape synchronization, FindBugs wasn't able to find this one, I had to track it down the old way, it caused the following test to fail on sparc: com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td . I believe I've found the cause, but won't be entirely sure until I run the tests on the old sparc again (might have to do it remotely, it's about 180km away). Anyway basically what appears to be happening is while the contents of sendQueue are being sent to open a connection to the server, other tasks are writing to the sendQueue, so the server on occassion ends up getting some other garbled info instead and doesn't respond, leaving the test hanging. So I think I've got it this time! Will commit soon. On 11/03/2013 6:13 PM, Dan Creswell wrote: 1412 passed, 46 skipped, 0 failures in about 58000 seconds. On 10 March 2013 13:26, Dan Creswell wrote: I'm currently running this and jtreg, I'll report back when it's done. JDK 7 on OS X 10.8.2... On 10 March 2013 13:17, Dennis Reedy wrote: I ran: ant qa.run [java] - [java] GENERAL HARNESS CONFIGURATION INFORMATION: [java] [java]Date started: [java] Sat Mar 09 08:19:09 EST 2013 [java]Installation directory of the JSK: [java] com.sun.jini.jsk.home=/Users/dreedy/dev/src/projects/river/qa-trunk [java]Installation directory of the harness: [java] com.sun.jini.qa.home=/Users/dreedy/dev/src/projects/river/qa-trunk/qa [java]Categories being tested: [java] categories=id loader policyprovider locatordiscovery activation config discoverymanager joinmanager url iiop jrmp reliability thread renewalmanager constraint export lookupdiscovery servicediscovery io security lookupservice renewalservice eventmailbox jeri start discoveryservice discoveryproviders javaspace txnmanager [java] - [java] ENVIRONMENT PROPERTIES: [java] [java]JVM information: [java] Java HotSpot(TM) 64-Bit Server VM, 23.7-b01, 64 bit VM mode [java] Oracle Corporation [java]OS information: [java] Mac OS X, 10.7.5, x86_64 [java] [java] [java] # of tests started = 1412 [java] # of tests completed = 1412 [java] # of tests skipped = 46 [java] # of tests passed= 1412 [java] # of tests failed= 0 [java] [java] - [java] [java]Date finished: [java] Sun Mar 10 00:45:27 EST 2013 [java]Time elapsed: [java] 59178 seconds On Mar 9, 2013, at 840PM, Peter Firmstone wrote: Recent test failures: Solaris sparc: com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td Ubuntu JDK7 com/sun/jini/test/impl/outrigger/leasing/UseTxnMgrSpaceLeaseTestRenewCancel.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest2.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest3.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest4.td com/sun/jini/test/impl/outrigger/transaction/BlockingOnDeadTransactionTest.td Ubuntu Arm embedded com/sun/jini/test/impl/outrigger/leasing/UseNotifyLeaseTestRenewShutdown.td Ubuntu jdk6 com/sun/jini/test/spec/javaspace/conformance/ExpirationNotifyTest.td There are some remaining issues relating to unsafe publication, identified by find bugs (calling Thread.start() during construction), I'll fix these during the week, the failed jrmpexporter tests simply seem to be tests starting before previous tests sockets have been released by the OS. The remaining issues appear to be JavaSpace related. Regards, Peter. Dan Creswell wrote: I'm headed back to the UK so can test OS X in a couple of days if that's still useful... On 7 March 2013 05:25, Peter Firmston
Re: Development Progress update.
Cool, Thanks Dennis, Dan & Bryan, we're getting there! Bryan experienced two test failures on OSX: com/sun/jini/test/impl/start/CodebaseTest.td caused by: [java] CodebaseTest.run FINE: expected codebase for test service 1 proxy: http://Bryan-Thompson-MacBook-Air.local:9082/qa1-start-testservice1-dl.jar http://Bryan-Thompson-MacBook-Air.local:9082/qa1-start-testservice-common-dl.jar [java] CodebaseTest.run FINE: actual codebase for test service 1 proxy: http://bryan-thompson-macbook-air.local:9082/qa1-start-testservice1-dl.jar http://bryan-thompson-macbook-air.local:9082/qa1-start-testservice-common-dl.jar I've fixed it locally so both codebase strings are normalised, I'll upload the fix soon. The other: com/sun/jini/test/spec/javaspace/conformance/snapshot/SnapshotExpirationNotifyTest.td [java] Test Failed: Test Failed: com.sun.jini.qa.harness.TestException: Not all listeners've got expected number of events. I'm hoping that this is caused by the following bug I've discovered in com.sun.jini.jeri.internal.mux.StreamConnectionIO The LinkedList sendQueue access is synchronized with Mux.muxLock, unfortunately sendQueue's reference was copied to an instance variable and allowed to escape synchronization, FindBugs wasn't able to find this one, I had to track it down the old way, it caused the following test to fail on sparc: com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td . I believe I've found the cause, but won't be entirely sure until I run the tests on the old sparc again (might have to do it remotely, it's about 180km away). Anyway basically what appears to be happening is while the contents of sendQueue are being sent to open a connection to the server, other tasks are writing to the sendQueue, so the server on occassion ends up getting some other garbled info instead and doesn't respond, leaving the test hanging. So I think I've got it this time! Will commit soon. On 11/03/2013 6:13 PM, Dan Creswell wrote: 1412 passed, 46 skipped, 0 failures in about 58000 seconds. On 10 March 2013 13:26, Dan Creswell wrote: I'm currently running this and jtreg, I'll report back when it's done. JDK 7 on OS X 10.8.2... On 10 March 2013 13:17, Dennis Reedy wrote: I ran: ant qa.run [java] - [java] GENERAL HARNESS CONFIGURATION INFORMATION: [java] [java]Date started: [java] Sat Mar 09 08:19:09 EST 2013 [java]Installation directory of the JSK: [java] com.sun.jini.jsk.home=/Users/dreedy/dev/src/projects/river/qa-trunk [java]Installation directory of the harness: [java] com.sun.jini.qa.home=/Users/dreedy/dev/src/projects/river/qa-trunk/qa [java]Categories being tested: [java] categories=id loader policyprovider locatordiscovery activation config discoverymanager joinmanager url iiop jrmp reliability thread renewalmanager constraint export lookupdiscovery servicediscovery io security lookupservice renewalservice eventmailbox jeri start discoveryservice discoveryproviders javaspace txnmanager [java] - [java] ENVIRONMENT PROPERTIES: [java] [java]JVM information: [java] Java HotSpot(TM) 64-Bit Server VM, 23.7-b01, 64 bit VM mode [java] Oracle Corporation [java]OS information: [java] Mac OS X, 10.7.5, x86_64 [java] [java] [java] # of tests started = 1412 [java] # of tests completed = 1412 [java] # of tests skipped = 46 [java] # of tests passed= 1412 [java] # of tests failed= 0 [java] [java] - [java] [java]Date finished: [java] Sun Mar 10 00:45:27 EST 2013 [java]Time elapsed: [java] 59178 seconds On Mar 9, 2013, at 840PM, Peter Firmstone wrote: Recent test failures: Solaris sparc: com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td Ubuntu JDK7 com/sun/jini/test/impl/outrigger/leasing/UseTxnMgrSpaceLeaseTestRenewCancel.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest2.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest3.td com/sun/jini/test/spec/jrmp/jrmpexporter/Unexport_BehaviorTest4.td com/sun/jini/test/impl/outrigger/transaction/BlockingOnDeadTransactionTest.td Ubuntu Arm embedded com/sun/jini/test/impl/outrigger/leasing/UseNotifyLeaseTestRenewShutdown.td Ubuntu jdk6 com/sun/jini/test/spec/javaspace/conformance/ExpirationNotifyTest.td There are some remaining issues relating to unsafe publication, identified by find bugs (calling Thread.start() during construction), I'll fix these during the week, the failed jrmpexporter tests simply seem to be tests starting before previous tests sockets have been released by the OS. The remaining issues appear to be JavaSpace related. Regards, Peter. Dan Creswell wrote: I'm headed back to the UK so can test OS X in a couple of days if that's still useful... On 7 March 2013 05:25, Peter Firmston
