Hi Rick Follow on … And here is the result for
rexx testOORexx -s -X native_API ooTest Framework - Automated Test of the ooRexx Interpreter Interpreter: REXX-ooRexx_5.0.0(MT)_64-bit 6.05 1 Dec 2018 OS Name: DARWIN SysVersion: Darwin Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64.17.7.0 Tests ran: 22398 Assertions: 375210 Failures: 0 Errors: 0 File search: 00:00:01.205401 Suite construction: 00:00:00.979385 Test execution: 00:03:00.447461 Total time: 00:03:02.941318 [enrico@enrico-imac ooRexx.testsuite]$ Enrico > On 2 Dec 2018, at 13:59, Rick McGuire <object.r...@gmail.com> wrote: > > These tests have been driving me crazy, not because there are failures, but > because there are successes. Two of the six test methods in that group are > passing, and if there was a problem with the daemon, I would have expected > all of the rxqueue tests to fail for the same reason. I have noticed a key > difference between the failing tests and the passing tests. All of the > failing tests are using a Rexx program called as a command to generate the > output and the passing tests are just using type or cat to produce the > output. I'm wondering if some of the proceeding tests in the test suite are > somehow changing the environment such that the rexx command is failing. When > the testgroup is run on its own, those changes don't occur and everything > passes. > > Could your try adding a "::options trace commands" directive to the test > group and run both ways so I can see what commands are getting issued? > Unfortunately, the return code from piped commands are lost because of the > piping...that would have been useful information too. > > Rick > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
