"Boing-Boing" means that the machine produces a noise „boing!“ five times in a row at exactly the time I see a space instead of a dot in the execution output. I cannot describe it better than that, it must be an error raised. I will try to pinpoint each error.
Von meinen Macbook gesendet Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 19.11.2018 um 20:13 schrieb P.O. Jonsson <oor...@jonases.se>: > > Dear Eric, thanks for responding, answer below inline. > > Von meinen Macbook gesendet > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se <mailto:oor...@jonases.se> > > > >> Am 19.11.2018 um 19:09 schrieb Erich Steinböck <erich.steinbo...@gmail.com >> <mailto:erich.steinbo...@gmail.com>>: >> >> Hi P.O., >> good practice is to run tests with `testOORexx -s -X native_API` >> If in addition if you suppress long-running tests with e. g. `-x CHAROUT >> TIME Alarm Message ticker WindowsEventLog` tests will finish in a minute or >> less. >> > > I will try with -X native_API > >> When something goes wrong, the last test group printed should be the >> offender, in your case Macrospace.testGroup. What happens when you run it >> stand-alone? >> > > I have enclosed a run with that test, it aborts without a result. > >> the machine goes boing-boing five times >> Please explain what "boing-boing" means >> >> REX121: Storage for data queues is exhausted >> Which test group raises this error? This may point to an issue with rxap >> > There are more than one place, I will look further > >> cat: stdout: Broken pipe >> Which test group raises this error? >> > Same here, I need to pinpoint it > >> >> On Mon, Nov 19, 2018 at 5:18 PM P.O. Jonsson <oor...@jonases.se >> <mailto:oor...@jonases.se>> wrote: >> I also just found out what Rony just wrote, here are some options >> >> Output control: >> -l -DlogFile=FILE Put test results in log file FILE >> -L -DlogFileAppend=bool Append test results to log file >> -s -DshowProgress=bool Show test group progress >> -S -DshowTestcases=bool Show test case progress >> -u -DsuppressTestcaseTicks=bool Do not show ticks during test execution >> -U -DsuppressAllTicks=bool Do not show any ticks >> -V, -Dverbosity=NUM Set vebosity to NUM >> -w, -DwaitAtCompletion=bool At test end, wait for user to hit enter >> >> with this information I could get a bit further, a potential problem (I >> think) is the need to use ./ to refer to the testcases on Mac (deprecated)? >> >> This works now: >> >> testOORexx.rex -R ./ooRexx/base/expressions -s -S >> >> -s and -S was enough to see that is was running and in the end I got a result >> >> 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: 2913 >> Assertions: 5387 >> Failures: 0 >> Errors: 0 >> >> File search: 00:00:00.066862 >> Suite construction: 00:00:00.103980 >> Test execution: 00:00:00.860958 >> Total time: 00:00:01.468976 >> >> However, and this is weird, If I broaden the test >> >> testOORexx.rex -R ./ooRexx/base -s -S >> >> The tests start to run and I get some 100 test classes run, but somewhere >> along the line the machine goes boing-boing five times (and I see five >> spaces instead of dots, like this (..................... ……………..) and >> then I need to break out of it or wait until it finishes without result. >> >> I have enclosed a listing of the output, does not know if it helps. >> >> Advice on what to do next highly appreciated >> >> >> Von meinen Macbook gesendet >> >> Hälsningar/Regards/Grüsse, >> P.O. Jonsson >> oor...@jonases.se <mailto:oor...@jonases.se> >> >> >> >>> Am 19.11.2018 um 16:29 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at >>> <mailto:rony.flatsc...@wu.ac.at>>: >>> >>> Bruce, >>> >>> On 19.11.2018 16:14, CV Bruce wrote: >>>> Does anyone know if there is a “verbose” option that would print out test >>>> results as each test is performed? That way we can at least see where we >>>> are dying. >>> you can see the most important switches with: >>> testOORexx --help >>> So the switch "-S" (capital S) will sho you the execution of the individual >>> test cases. >>> >>> HTH, >>> >>> ---rony >>> >>>> On Nov 18, 2018, at 3:45 PM, P.O. Jonsson <oor...@jonases.se >>>> <mailto:oor...@jonases.se>> wrote: >>>>> >>>>> 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 <mailto:oor...@jonases.se> >>>>> >>>>> >>>>> >>>>>> Am 18.11.2018 um 21:05 schrieb CV Bruce <cvbr...@gmail.com >>>>>> <mailto:cvbr...@gmail.com>>: >>>>>> >>>>>> 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 <oor...@jonases.se >>>>>>> <mailto:oor...@jonases.se>> 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 <cvbr...@gmail.com >>>>>>> <mailto:cvbr...@gmail.com>>: >>>>>>> >>>>>>>> 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 <cvbr...@gmail.com >>>>>>>>> <mailto:cvbr...@gmail.com>> 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 <oor...@jonases.se >>>>>>>>>> <mailto:oor...@jonases.se>> wrote: >>>>>>>>>> >>>>>>>>>> Dear Developers, >>>>>>>>>> >>>>>>>>>> I have downloaded the test environment from : >>>>>>>>>> https://svn.code.sf.net/p/oorexx/code-0/test/trunk >>>>>>>>>> <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 <mailto:oor...@jonases.se> >>>>>>>>>> >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto:Oorexx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto:Oorexx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > <macrospace run on mac.txt> > _______________________________________________ > 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
