Re: [Oorexx-devel] test case rexxtry

> Am 21.02.2021 um 17:52 schrieb Erich Steinböck : > > Hi P.O., > > > \Microsoft was unexpected at this time. > > I cannot figure out what is wrong in this call? > In my setbuild.bat I can successfully run vcvarsall.bat like this: > > call "C:\Program Files (x86)\Microsoft Visual > Studio\2017\

Re: [Oorexx-devel] test case rexxtry

Hi P.O., > \Microsoft was unexpected at this time. > I cannot figure out what is wrong in this call? In my setbuild.bat I can successfully run vcvarsall.bat like this: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 *

Re: [Oorexx-devel] test case rexxtry

> Am 19.02.2021 um 19:29 schrieb Rick McGuire : > > > > On Fri, Feb 19, 2021 at 1:19 PM P.O. Jonsson > wrote: > Hi René, > > During the build process rexxtry.rex is moved (not copied) from /samples to > /bin, so despite being a samples it resides in the directory whe

Re: [Oorexx-devel] test case rexxtry

On Fri, Feb 19, 2021 at 1:19 PM P.O. Jonsson wrote: > Hi René, > > During the build process rexxtry.rex is moved (not copied) from /samples > to /bin, so despite being a samples it resides in the directory where the > executables are. So it beats me how you can test rexx itself but not > rexxtry

Re: [Oorexx-devel] test case rexxtry

Hi René, During the build process rexxtry.rex is moved (not copied) from /samples to /bin, so despite being a samples it resides in the directory where the executables are. So it beats me how you can test rexx itself but not rexxtry when they reside in the same place? That said: the only test

Re: [Oorexx-devel] test case rexxtry

Yes, but my point is, I don’t want that. I do want the tests to succeed on a non-installed build. I don’t think being able to find rexxtry.rex is a test for a working interpreter. If we want to test the lookup facility, we should specify a file that is, or needs to be on the $PATH. There are lot

Re: [Oorexx-devel] test case rexxtry

On 19.02.2021 15:28, rvjan...@xs4all.nl wrote: > Ok, will add it to the path like P.O. suggested and hope that it works. Or > will copy it after the build. I think it tests the install process and not > the working of the interpreter. You can test the existence of rexxtry.rex next to rexx[.exe]

Re: [Oorexx-devel] test case rexxtry

Ok, will add it to the path like P.O. suggested and hope that it works. Or will copy it after the build. I think it tests the install process and not the working of the interpreter. René. > On 19 Feb 2021, at 14:55, Rony G. Flatscher wrote: > > On 18.02.2021 15:49, René Jansen wrote: >> Ther

Re: [Oorexx-devel] test case rexxtry

On 18.02.2021 15:49, René Jansen wrote: > There is currently only one test case failing on the Linux on Z Rockhopper, > which is the test for the reachability of RexxTry. This is because this is > the uninstalled version of ooRexx - the so-called USB version. I expect this > to fail on other mac

Re: [Oorexx-devel] test case rexxtry

Dear René, One further option would be to include the path to the samples when setting up the test environment. This is currently not the case (and thus the only test month.testGroup is not found) but I intend to fix that, I just wanted to clean out some things first and got diverted...(see my

Re: [Oorexx-devel] test case rexxtry

If you append the path to the samples to the path of your machine, does it pass then? If so you can add that to Jenkins build Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 18.02.2021 um 15:49 schrieb René Jansen : > > There is currently only one test case failing on the Linux