I am grateful for any hint, I will try the exec thingy. Be aware that for some of the samples you do need to move to where the samples are located & run to get the correct behavior, this might cause problems. Also the client-server tests are a bit tricky and on some of my Linuxes they do not even run, I guess because my installation is missing some required plugin. There is plenty of room for improvement :-)
Regarding running sudo-free this may not be a big problem if we set up a VM to run on the Jenkins master itself, there is plenty of capacity left, it is idling 23 hrs per day. Behind the firewall it would not be exposed to the outside world at all. 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
