Re: [Oorexx-devel] errors that are NOT really Rexx errors

2019-02-15 Thread P.O. Jonsson
As I said, I think it has to do with sysFileTree(); I had problems in other programs as well. If that function is used to look for the test cases then 0 is the result. I am talking about macOS only, I have not tested on other systems yet. Hälsningar/Regards/Grüsse, P.O. Jonsson

Re: [Oorexx-devel] errors that are NOT really Rexx errors

2019-02-15 Thread Enrico Sorichetti via Oorexx-devel
It is not a problem with the test suite … It happens also with the test suite at the 11724 level E > On 15 Feb 2019, at 16:33, P.O. Jonsson wrote: > > I have now tested the lates committed changes in r11760 > > Compiling on macOS works fine but running the test suite with the same >

Re: [Oorexx-devel] errors that are NOT really Rexx errors

2019-02-15 Thread P.O. Jonsson
I have now tested the lates committed changes in r11760 Compiling on macOS works fine but running the test suite with the same revision breaks out after 1 failing test. REXX-ooRexx_5.0.0(MT)_64-bit 6.05 15 Feb 2019 r11760 Searching for test containers.. Executing automated test suite ooTest

Re: [Oorexx-devel] errors that are NOT really Rexx errors

2019-02-15 Thread P.O. Jonsson
In test suite from today 11759 there is a modified setTestEnv.sh only considering Linux, probably a local version from a developer. Also OOREXXUNIT.CLS is modified. I tried replacing both with yesterdays version but to no avail. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se >

[Oorexx-devel] errors that are NOT really Rexx errors

2019-02-15 Thread Enrico Sorichetti via Oorexx-devel
Just to let You all know Running the test suite Expected: [[REXX-ooRexx_5.0.0(MT)_64-bit 6.05 14 Feb 2019], identityHash="-34387144817"] Actual: [[REXX-ooRexx_5.0.0(MT)_64-bit 6.05 13 Feb 2019], identityHash="-34383169473"] Message: .RexxInfo~name should be equal to parse