Re: [Oorexx-devel] release 5 wiki

[P.O. Jonsson]

Dear René, this seems to work, I just edited the page and could remove what I 
had written so good for now.

The steps for how to build your own installation would fit better in 
https://sourceforge.net/p/oorexx/wiki/how-to-build-oorexx/ 
 It is the same 
steps as set out for Win and Ubuntu, just for Mac. But that could be moved 
later. Before I do anything I will make a complete recheck and repeat all the 
step on a machine with Mojave freshly installed.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 19.11.2018 um 03:48 schrieb René Jansen :
> 
> Hi P.O.,
> 
> it took some time, but I added you as a ‘member’ of the project; you are the 
> first in this category. The intention is that you can edit the wiki’s; please 
> let me know if otherwise.
> 
> best regards,
> 
> René.
> 
>> On 16 Nov 2018, at 14:38, P.O. Jonsson > > wrote:
>> 
>> Dear René,
>> 
>> I have userID perolovjonsson on sourceforge.
>> 
>> I have written a WIKI on how to make your own ooRexx on the MAC, with all 
>> the steps. I just need to finalize the last step and I will put it there, 
>> same for the installer(s)
>> 
>> I will be OK from now and some time so I might not respond on any message ok?
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>> 
>>> Am 16.11.2018 um 17:12 schrieb René Jansen >> >:
>>> 
>>> Hi P.O.,
>>> 
>>> I added a wiki on sourceforge for the release roadmap at 
>>> https://sourceforge.net/p/oorexx/rel5wiki/Home/ 
>>>  . The sole item for now 
>>> is the mac installer. Could you drop the script for the .dmg installer in 
>>> there?
>>> To do that you need access. Do you have a SourceForge ID? Please let me 
>>> know so I can add you to the wiki editors.
>>> 
>>> Everyone: feel free to add other actions we need before releasing the beta.
>>> 
>>> best regards,
>>> 
>>> René.
>>> 
>>> 
>>> ___
>>> 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
> 
> ___
> 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

Re: [Oorexx-devel] release 5 wiki

[René Jansen]

Hi P.O.,

it took some time, but I added you as a ‘member’ of the project; you are the 
first in this category. The intention is that you can edit the wiki’s; please 
let me know if otherwise.

best regards,

René.

> On 16 Nov 2018, at 14:38, P.O. Jonsson  wrote:
> 
> Dear René,
> 
> I have userID perolovjonsson on sourceforge.
> 
> I have written a WIKI on how to make your own ooRexx on the MAC, with all the 
> steps. I just need to finalize the last step and I will put it there, same 
> for the installer(s)
> 
> I will be OK from now and some time so I might not respond on any message ok?
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
>> Am 16.11.2018 um 17:12 schrieb René Jansen > >:
>> 
>> Hi P.O.,
>> 
>> I added a wiki on sourceforge for the release roadmap at 
>> https://sourceforge.net/p/oorexx/rel5wiki/Home/ 
>>  . The sole item for now is 
>> the mac installer. Could you drop the script for the .dmg installer in there?
>> To do that you need access. Do you have a SourceForge ID? Please let me know 
>> so I can add you to the wiki editors.
>> 
>> Everyone: feel free to add other actions we need before releasing the beta.
>> 
>> best regards,
>> 
>> René.
>> 
>> 
>> ___
>> 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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Running Testcases

[P.O. Jonsson]

dear Bruce,

I have updated using svn to todays built r11519, created an installer and 
installed a working installation of ooRexx. I have also downloaded the 
corresponding test folder structure: 

oorexx-code-0-r11519-test-trunk/

Then I move into oorexx-code-0-r11519-test-trunk/

and set up the environment

bash setTestEnv.sh

After that I can run a single test (the example in readme.first uses a partial 
path, this is not something I invented so don’t shoot me ok?)

rexx testOORexx.rex -R ./ooRexx/base/expressions -f Addition

This produces the desired output

POs-MacBook-Pro:oorexx-code-0-r11519-test-trunk po$ rexx testOORexx.rex -R 
./ooRexx/base/expressions -f Addition
Searching for test containers..
Executing automated test suite..

ooTest Framework - Automated Test of the ooRexx Interpreter

Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 18 Nov 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:  200
Assertions: 304
Failures:   0
Errors: 0

File search:00:00:00.010274
Suite construction: 00:00:00.005753
Test execution: 00:00:00.016902
Total time: 00:00:01.013693

I can then do the same for a whole set of tests

rexx testOORexx.rex -R ./ooRexx/base/expressions

BUT, when I try to run the whole suite like this:

rexx testOORexx

I get stuttering dots every second and after some time things like this

oorexx-code-0-r11519-test-trunk po$ rexx testOORexx.rex
Searching for test containers
Executing automated test suite.
REX121: Storage for data queues is exhausted.
.
REX121: Storage for data queues is exhausted.

REX121: Storage for data queues is exhausted.
cat: stdout: Broken pipe
.

And I have to kill a rexx process manually to get it stopped.

It seems to me that when I do not find the test the program gets out of control,

Please advice how to refer to the whole set of test cases, I tried some 
variants, but failed.




Von meinen Macbook gesendet

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 18.11.2018 um 21:05 schrieb CV Bruce :
> 
> That depends. you need to pull ooTest from the same build level, I believe.
> 
> Bruce
>> On Nov 18, 2018, at 11:50 AM, P. O. Jonsson > > wrote:
>> 
>> Thanks for the info, I have done it the way you proposed including the shell 
>> script but I have an older build of ooRexx, can that be the problem?
>> 
>> I will try further tomorrow, thanks for all the feedback.  
>> Hälsningar/Regards/Grüsse,
>> P. O. Jonsson
>> Von meinem iPhone gesendet
>> 
>> Am 18.11.2018 um 20:07 schrieb CV Bruce > >:
>> 
>>> I looked at some of my runs from many years ago, and the run time was less 
>>> then three minutes.  Also, after a test run be sure that all of the files 
>>> created during the test run are deleted.  They should be, but double check. 
>>>  Also my prior comment (off line) regarding RXAPI.  It is probably best to 
>>> kill it and restart it manually so that you can be sure that you are 
>>> getting the version that was from the current build. 
>>> 
>>> Bruce
 On Nov 18, 2018, at 10:48 AM, CV Bruce >>> > wrote:
 
 It’s been a while since I’ve run the test suite, but it shouldn’t take 
 more than 15 minutes or so.
 
 In the past, I’ve run into the situation that you have, and it generally 
 means that either your invocation or your environment isn’t set up 
 correctly.
 
 Bruce
> On Nov 18, 2018, at 10:41 AM, P.O. Jonsson  > wrote:
> 
> Dear Developers,
> 
> I have downloaded the test environment from : 
> https://svn.code.sf.net/p/oorexx/code-0/test/trunk 
>  as suggested by Rick 
> and have started to run the available test cases (on a Mac). It has now 
> been running for four hours and I wonder what the expected completion 
> time is on a decent i5 machine? There is no lack of memory (11 from 16 GB 
> still available) and the machine is in average 95% idling. Should I abort 
> and try a subset first or is it normal to have these runtimes? I have 
> seen that there are many many tests. The „dots“ go on for another page or 
> so. I will do the same on a Win machine to see if there is a difference 
> but some input is welcome on what to expect. I have run the shell script 
> to set up the test environment and I have done what is set out in 
> readme.first.
> 
> Os-MacBook-Pro:oorexx-code-0-r11517-test-trunk po$ rexx testOORexx.rex -X 
> native_API
> Searching for test containers...
> Executing automated test 
> suite..
> . 
> ..
> 

Re: [Oorexx-devel] Running Testcases

[CV Bruce]

That depends. you need to pull ooTest from the same build level, I believe.

Bruce
> On Nov 18, 2018, at 11:50 AM, P. O. Jonsson  wrote:
> 
> Thanks for the info, I have done it the way you proposed including the shell 
> script but I have an older build of ooRexx, can that be the problem?
> 
> I will try further tomorrow, thanks for all the feedback.  
> Hälsningar/Regards/Grüsse,
> P. O. Jonsson
> Von meinem iPhone gesendet
> 
> Am 18.11.2018 um 20:07 schrieb CV Bruce  >:
> 
>> I looked at some of my runs from many years ago, and the run time was less 
>> then three minutes.  Also, after a test run be sure that all of the files 
>> created during the test run are deleted.  They should be, but double check.  
>> Also my prior comment (off line) regarding RXAPI.  It is probably best to 
>> kill it and restart it manually so that you can be sure that you are getting 
>> the version that was from the current build. 
>> 
>> Bruce
>>> On Nov 18, 2018, at 10:48 AM, CV Bruce >> > wrote:
>>> 
>>> It’s been a while since I’ve run the test suite, but it shouldn’t take more 
>>> than 15 minutes or so.
>>> 
>>> In the past, I’ve run into the situation that you have, and it generally 
>>> means that either your invocation or your environment isn’t set up 
>>> correctly.
>>> 
>>> Bruce
 On Nov 18, 2018, at 10:41 AM, P.O. Jonsson >>> > wrote:
 
 Dear Developers,
 
 I have downloaded the test environment from : 
 https://svn.code.sf.net/p/oorexx/code-0/test/trunk 
  as suggested by Rick 
 and have started to run the available test cases (on a Mac). It has now 
 been running for four hours and I wonder what the expected completion time 
 is on a decent i5 machine? There is no lack of memory (11 from 16 GB still 
 available) and the machine is in average 95% idling. Should I abort and 
 try a subset first or is it normal to have these runtimes? I have seen 
 that there are many many tests. The „dots“ go on for another page or so. I 
 will do the same on a Win machine to see if there is a difference but some 
 input is welcome on what to expect. I have run the shell script to set up 
 the test environment and I have done what is set out in readme.first.
 
 Os-MacBook-Pro:oorexx-code-0-r11517-test-trunk po$ rexx testOORexx.rex -X 
 native_API
 Searching for test containers...
 Executing automated test 
 suite..
 . 
 ..
 ...
 
 As a side remark: all rexx files (including the test case files in 
 /test/trunk have the shebang #!/usr/bin/rexx rather than #! /usr/bin/env 
 rexx
 
 PS the exercise with test cases for the samples is for me also a test to 
 benchmark the installer I am working on, so please bear with my qs
 
 Von meinen Macbook gesendet
 
 Hälsningar/Regards/Grüsse,
 P.O. Jonsson
 oor...@jonases.se 
 
 
 
 ___
 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 
>> 
> ___
> 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

Re: [Oorexx-devel] Running Testcases

[P. O. Jonsson]

Thanks for the info, I have done it the way you proposed including the shell 
script but I have an older build of ooRexx, can that be the problem?

I will try further tomorrow, thanks for all the feedback.  
Hälsningar/Regards/Grüsse,
P. O. Jonsson
Von meinem iPhone gesendet

> Am 18.11.2018 um 20:07 schrieb CV Bruce :
> 
> I looked at some of my runs from many years ago, and the run time was less 
> then three minutes.  Also, after a test run be sure that all of the files 
> created during the test run are deleted.  They should be, but double check.  
> Also my prior comment (off line) regarding RXAPI.  It is probably best to 
> kill it and restart it manually so that you can be sure that you are getting 
> the version that was from the current build. 
> 
> Bruce
>> On Nov 18, 2018, at 10:48 AM, CV Bruce  wrote:
>> 
>> It’s been a while since I’ve run the test suite, but it shouldn’t take more 
>> than 15 minutes or so.
>> 
>> In the past, I’ve run into the situation that you have, and it generally 
>> means that either your invocation or your environment isn’t set up correctly.
>> 
>> Bruce
>>> On Nov 18, 2018, at 10:41 AM, P.O. Jonsson  wrote:
>>> 
>>> Dear Developers,
>>> 
>>> I have downloaded the test environment from : 
>>> https://svn.code.sf.net/p/oorexx/code-0/test/trunk as suggested by Rick and 
>>> have started to run the available test cases (on a Mac). It has now been 
>>> running for four hours and I wonder what the expected completion time is on 
>>> a decent i5 machine? There is no lack of memory (11 from 16 GB still 
>>> available) and the machine is in average 95% idling. Should I abort and try 
>>> a subset first or is it normal to have these runtimes? I have seen that 
>>> there are many many tests. The „dots“ go on for another page or so. I will 
>>> do the same on a Win machine to see if there is a difference but some input 
>>> is welcome on what to expect. I have run the shell script to set up the 
>>> test environment and I have done what is set out in readme.first.
>>> 
>>> Os-MacBook-Pro:oorexx-code-0-r11517-test-trunk po$ rexx testOORexx.rex -X 
>>> native_API
>>> Searching for test containers...
>>> Executing automated test suite..
>>> . 
>>> ..
>>> ...
>>> 
>>> As a side remark: all rexx files (including the test case files in 
>>> /test/trunk have the shebang #!/usr/bin/rexx rather than #! /usr/bin/env 
>>> rexx
>>> 
>>> PS the exercise with test cases for the samples is for me also a test to 
>>> benchmark the installer I am working on, so please bear with my qs
>>> 
>>> Von meinen Macbook gesendet
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se
>>> 
>>> 
>>> 
>>> ___
>>> 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
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Running Testcases

[CV Bruce]

I looked at some of my runs from many years ago, and the run time was less then 
three minutes.  Also, after a test run be sure that all of the files created 
during the test run are deleted.  They should be, but double check.  Also my 
prior comment (off line) regarding RXAPI.  It is probably best to kill it and 
restart it manually so that you can be sure that you are getting the version 
that was from the current build. 

Bruce
> On Nov 18, 2018, at 10:48 AM, CV Bruce  wrote:
> 
> It’s been a while since I’ve run the test suite, but it shouldn’t take more 
> than 15 minutes or so.
> 
> In the past, I’ve run into the situation that you have, and it generally 
> means that either your invocation or your environment isn’t set up correctly.
> 
> Bruce
>> On Nov 18, 2018, at 10:41 AM, P.O. Jonsson > > wrote:
>> 
>> Dear Developers,
>> 
>> I have downloaded the test environment from : 
>> https://svn.code.sf.net/p/oorexx/code-0/test/trunk 
>>  as suggested by Rick 
>> and have started to run the available test cases (on a Mac). It has now been 
>> running for four hours and I wonder what the expected completion time is on 
>> a decent i5 machine? There is no lack of memory (11 from 16 GB still 
>> available) and the machine is in average 95% idling. Should I abort and try 
>> a subset first or is it normal to have these runtimes? I have seen that 
>> there are many many tests. The „dots“ go on for another page or so. I will 
>> do the same on a Win machine to see if there is a difference but some input 
>> is welcome on what to expect. I have run the shell script to set up the test 
>> environment and I have done what is set out in readme.first.
>> 
>> Os-MacBook-Pro:oorexx-code-0-r11517-test-trunk po$ rexx testOORexx.rex -X 
>> native_API
>> Searching for test containers...
>> Executing automated test suite..
>> . 
>> ..
>> ...
>> 
>> As a side remark: all rexx files (including the test case files in 
>> /test/trunk have the shebang #!/usr/bin/rexx rather than #! /usr/bin/env rexx
>> 
>> PS the exercise with test cases for the samples is for me also a test to 
>> benchmark the installer I am working on, so please bear with my qs
>> 
>> Von meinen Macbook gesendet
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>> ___
>> 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

Re: [Oorexx-devel] Running Testcases

[CV Bruce]

It’s been a while since I’ve run the test suite, but it shouldn’t take more 
than 15 minutes or so.

In the past, I’ve run into the situation that you have, and it generally means 
that either your invocation or your environment isn’t set up correctly.

Bruce
> On Nov 18, 2018, at 10:41 AM, P.O. Jonsson  wrote:
> 
> Dear Developers,
> 
> I have downloaded the test environment from : 
> https://svn.code.sf.net/p/oorexx/code-0/test/trunk 
>  as suggested by Rick and 
> have started to run the available test cases (on a Mac). It has now been 
> running for four hours and I wonder what the expected completion time is on a 
> decent i5 machine? There is no lack of memory (11 from 16 GB still available) 
> and the machine is in average 95% idling. Should I abort and try a subset 
> first or is it normal to have these runtimes? I have seen that there are many 
> many tests. The „dots“ go on for another page or so. I will do the same on a 
> Win machine to see if there is a difference but some input is welcome on what 
> to expect. I have run the shell script to set up the test environment and I 
> have done what is set out in readme.first.
> 
> Os-MacBook-Pro:oorexx-code-0-r11517-test-trunk po$ rexx testOORexx.rex -X 
> native_API
> Searching for test containers...
> Executing automated test suite..
> . 
> ..
> ...
> 
> As a side remark: all rexx files (including the test case files in 
> /test/trunk have the shebang #!/usr/bin/rexx rather than #! /usr/bin/env rexx
> 
> PS the exercise with test cases for the samples is for me also a test to 
> benchmark the installer I am working on, so please bear with my qs
> 
> Von meinen Macbook gesendet
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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

[Oorexx-devel] Running Testcases

[P.O. Jonsson]

Dear Developers,

I have downloaded the test environment from : 
https://svn.code.sf.net/p/oorexx/code-0/test/trunk 
 as suggested by Rick and 
have started to run the available test cases (on a Mac). It has now been 
running for four hours and I wonder what the expected completion time is on a 
decent i5 machine? There is no lack of memory (11 from 16 GB still available) 
and the machine is in average 95% idling. Should I abort and try a subset first 
or is it normal to have these runtimes? I have seen that there are many many 
tests. The „dots“ go on for another page or so. I will do the same on a Win 
machine to see if there is a difference but some input is welcome on what to 
expect. I have run the shell script to set up the test environment and I have 
done what is set out in readme.first.

Os-MacBook-Pro:oorexx-code-0-r11517-test-trunk po$ rexx testOORexx.rex -X 
native_API
Searching for test containers...
Executing automated test suite..
. ..
...

As a side remark: all rexx files (including the test case files in /test/trunk 
have the shebang #!/usr/bin/rexx rather than #! /usr/bin/env rexx

PS the exercise with test cases for the samples is for me also a test to 
benchmark the installer I am working on, so please bear with my qs

Von meinen Macbook gesendet

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building test cases

[J Leslie Turriff]

On 2018-11-16 09:19:07 René Jansen wrote:
> No, it is not, in the second example the env executable looks if there is a
> rexx on the path, the first looks for a /usr/bin/env/rexx executable.
>
> My proposal:
>
> Let’s get rid of the shebang; it outlived its usefulness
>
> 1) most people I know type rexx [exec name]
> 2) on windows there is a mechanism to trigger filename suffices to an
> executable; it is not often used 3) most modern unix shells like bash and
> zsh have a mechanism to alias a suffix to an executable; this is what I and
> my friends use
>
> So in short, it is not used, it is not needed, it makes for a lot of
> discussion.
>
> Let’s hear if you agree with me that it is some bothersome thing from the
> past. (And everybody who wants to use it on their system, can edit it in
> themselves).
>
> best regards,
>
> René.

1)  Those of us who do not type 'rexx [execname]' would not like to 
have to 
learn to do that. :-)
3)  Are you speaking here of the MIME extension-matching method, or 
the 
kernel-based binfmt_misc method?  It looks to me like the binfmg_misc would 
be more flexible; it doesn't require an explicit file extension, so it could 
work the way the original mainframe Rexx did, by matching content in the 
first line of the script.  (In CMS, just the appearance of /* was enough; in 
TSO, the word REXX had to appear. I always imbedded REXX in the top line of 
the documentation flowerbox in my code.)  Presumably the installer could 
insert an entry in the binfmt_misc registry.

Leslie


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel