On Wed, Aug 11, 2010 at 12:12 PM, Erico Mendonca <emendo...@novell.com> wrote:
> All right, my builds appear to be fine (executed with "./testOORexx.rex -X > native_API" as per README file). You can probably use -B and skip the -X to try and run the native API tests also. If your environment is set up to build, the exernal binaries should build on SLES. You would need to do: . ./setTestEnv.sh first. If the native API tests fail because the binaries don't get built, then go back to -X ... > > BUT, I'm getting error on TEST_006 on SLES 11SP1 if I try to use the same > build as SLES 11: > > ================= > > Test Framework - Automated Test of the ooRexx Interpreter > > > Interpreter: REXX-ooRexx_4.0.1(MT) 6.03 11 Aug 2010 > Addressing Mode: 32 > ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0 > > Tests ran: 18311 > Assertions: 573485 > Failures: 1 > Errors: 0 > Skipped files: 30 > > [failure] [20100811 15:59:19.440128] > svn: runknown Change date: unknown > Test: TEST_006 > Class: SocketClass.testGroup > File: /home/usuario/4.0.1/ooRexx/extensions/rxsock/socketClass.testGroup > Line: 116 > Failed: asserNotEquals > Expected: [[-1], identityHash="383805214"] \= [[-1], > identityHash="368840407"] > Actual: [[-1], identityHash="383805214"] = [[-1], > identityHash="368840407"] > > File search: 00:00:03.378014 > Suite construction: 00:00:01.404804 > Test execution: 00:05:17.488569 > Total time: 00:05:22.633103 > > ========== > > Any ideas? SLES 11 and 11SP1 shouldn't be that different. Well, network connections are inherently unreliable. <grin> The failure doesn't actually come from the test case, test case 6, itself, but from the initialization of the server socket. The test cases run very quickly. When test_005 ends, it sends a command to the server to stop. It seems to me that test_006 could start initializing the next server socket before the last one is completely shut down. Then the new socket might fail to bind. test_006 looks like this: ::method test_006 -- test client and server (small message) srvr = .server~new(self, self~host, self~port) call syssleep(1) call client self, self~host, self~port, 'This is test 006' call client self, self~host, self~port, 'stop' return You could change that to: ::method test_006 -- test client and server (small message) call syssleep(1) srvr = .server~new(self, self~host, self~port) call syssleep(1) call client self, self~host, self~port, 'This is test 006' call client self, self~host, self~port, 'stop' return and see if it then runs correctly. You can run just the single test group using: ./testOORexx.rex -f ooRexx/extensions/rxsock/socketClass.testGroup. In fact, I'd just try that first, before changing the test group file. Just to see. Not all the tests are 100% robust. -- Mark Miesfeld ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
