Hi Erich, I have just committed the first test case where I have tried to do what you specified, let me know if synchronosconcurrency.testGroup is ok.
I wonder if the last line options all syntax should be in or not? Anything else? Regarding cd/rexx: for this particular test case you need to be running it from where the samples actually reside; the sample have a hardcoded read in of a text file that is used, hence the CD to that place and CD back. I use execRexxPrg to actually run the sample. This sample runs fine on macOS, also 100 times in a row, but gets stuck quite frequently on Windows (worse for 32 bit than 64 bit) and the same for Debian. Not sure why, running the sample itself seems to run just fine. IF you have any ideas on how to test this let me know. I will deal with the other test cases when you give this one green light. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 24.03.2021 um 20:52 schrieb Erich Steinböck <erich.steinbo...@gmail.com>: > > > Regarding your more recent change to the framework: It seem these changes > > did not give the same functionality on Linux, several samples test cases > > are now broken > Right, here's is why: > The changes I've done should enable us to run tests directly off the build > tree without having to install (and without touching any installed ooRexx). > This will help us run on slaves even when we don't have sudo (we really > shouldn't require no sudo any more). > To test whether things work as envisioned I've actually removed the installed > ooRexx from my Ubuntu VM. > This is why I believe running the samples through execRexxPrg() and not via > cd / rexx will fix this. > > I guess I'll need to verify this. > _______________________________________________ > 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
