Michael, testing on Ubuntu 16.04, this scenario runs clean for me:
Interpreter: REXX-ooRexx_4.2.0(MT)_64-bit 6.04 29 Dec 2013
Addressing Mode: 64
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0
Tests ran: 19379
Assertions: 576663
Failures: 0
Errors: 0
Skipped files: 33
File search: 00:00:01.981577
Suite construction: 00:00:01.078879
Test execution: 00:02:06.920122
Total time: 00:02:10.053668
Executing tests from /home/mdlueck/Documents/.../base/bif/SUBWORD.testGroup
> Killed
>
Where does "Killed" come from? I don't think I've ever seen such a message
for a Rexx exception
You can try to skip failing tests by adding e. g. "-x SUBWORD
second-test-to-skip third-to-skip" to the command "rexx ./testOORexx.rex -s
-X native_API"
File: /home/mdlueck/Documents/.../base/class/MutableBuffer/space.testGroup
> Expected: [[§äè °üé], identityHash="17515141932308"]
> Actual: [[§��è °��é], identityHash="17515105402628"]
>
These similar errors all point to a code-page issue: "ä" is encoded as two
bytes, instead of a single code-point
File: /home/mdlueck/Documents/test42/ooRexx/base/class/Stream.testGroup
> Expected: [[0], identityHash="17515161432122"]
> Actual: [[-1], identityHash="17515161583106"]
> Message: Check for root must succeed
>
Here it seems that Rexx has no working shell available
Can you try rexx -e " 'id -u' " and tell us the result?
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
