Re: [Oorexx-devel] Testing for future releases

> Am 22.05.2025 um 11:41 schrieb Rony G. Flatscher : > > On 20.05.2025 18:03, ooRexx wrote: >> I just realized that /main/branches/5.1.0/ was moved to >> /main/releases/5.1.0/, not copied, as it was done in earlier releases, >> including 5.0. What is the rationale behind that? I intended to u

Re: [Oorexx-devel] Testing for future releases

On 20.05.2025 18:03, ooRexx wrote: I just realized that /main/branches/5.1.0/  was */moved/* to /main/releases/5.1.0/, not */copied/*, as it was done in earlier releases, including 5.0. What is the rationale behind that? I intended to use it for a further release test, now that is not possible :

[Oorexx-devel] Testing for future releases

I just realized that /main/branches/5.1.0/ was moved to /main/releases/5.1.0/, not copied, as it was done in earlier releases, including 5.0. What is the rationale behind that? I intended to use it for a further release test, now that is not possible :-( IMO the /main/branches/5.X.Y should sta

Re: [Oorexx-devel] Testing ooRexx on Jenkins Windows machine

> Am 24.02.2021 um 18:15 schrieb Erich Steinböck : > > > is the Windows testing supposed to be running from the build directory > > rather than from the installation? > Yes, on Windows we run tests directly from the build. > The test job just adds the build directory to its PATH, like this > set

Re: [Oorexx-devel] Testing ooRexx on Jenkins Windows machine

> is the Windows testing supposed to be running from the build directory rather than from the installation? Yes, on Windows we run tests directly from the build. The test job just adds the build directory to its PATH, like this set PATH=..\..\ooRexx-windows64-build\oorexxBuild\bin;%PATH% This was

[Oorexx-devel] Testing ooRexx on Jenkins Windows machine

Dear all, I added some further examples to a sample usecomp.rex and at the same time added tests for these examples in usecomp.testGroup. I was surprised to find that Windows failed the test and when I checked it was referring to an older version of the sample. The current source code revision

[Oorexx-devel] Testing successfully doc->fo on Ubuntu (Re: Documentation on Jenkins

O.K., could get a proof-of-concept doc->fo working on Ubuntu without having to install anything on Ubuntu. Steps: * copy Gil's xsl-files to a temporary directory * adjust DOCPATH in the following script doc2fo.sh: #!/bin/sh DOCPATH=~/dev/oorexx-code-0/docs/trunk COMMON_SOURCE_SP

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

many to choose from." -Chip- Original message From: Jason Martin Date: 2/16/19 13:50 (GMT-05:00) To: Enrico Sorichetti via Oorexx-devel Subject: Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766 I know, knew, just say

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

The problem is that there is no automatic way to find out to such detail Just run … cmake --system-information [file] = Dump information about this system. To see what cmake can find out about Your system E > On 16 Feb 2019, at 21:07, Gil Barmwater wrote: > > I was just suggesting that if

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

Let me try again.  When a user wants to install ooRexx on his platform, he goes to SF and looks in the Files section under the ooRexx tab for the most recent file with a name that matches his platform, downloads it and uses the appropriate installation mechanism for that platform.  I was just s

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

Funny … after setting a missing CPACK variable Before ooRexx-5.0.0-11767.x86_64.deb The name had a reference to the svn revision After ooRexx-5.0.0-Linux.deb Nothing Weird ??? E ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net htt

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

MT-05:00) To: Enrico Sorichetti via Oorexx-devel Subject: Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766 I know, knew, just saying even standards are not standard.___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.s

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

something built on a certain a platform WILL NOT run on a different one LINUX will be even more selective There are subtle differences between the different distributions And there are also common practices to deal with … xx.deb is likely a package for Debian family system x.rpm i

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

That’s only the platform it was built on, not necessarily the one it’s running on. On Sat, Feb 16, 2019 at 2:14 PM Gil Barmwater wrote: > OK, so CMAKE "knows" the PLATFORM_ID which, I'm guessing, is used to > generate the name of the ooRexx installation file; e.g. > ooRexx-5.0.0-11742.centos7.x8

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

I guess not … From my tests they create something . ooRexx-5.0.0-Linux.sh ooRexx-5.0.0-Linux.tar.Z ooRexx-5.0.0-Linux.tar.gz I did it on Fedora but the result is exactly the same for Debian For the other tests I run I got the same layout with Darwin, FreeBSD, OpenBSD, instead of Linux Just t

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

OK, so CMAKE "knows" the PLATFORM_ID which, I'm guessing, is used to generate the name of the ooRexx installation file; e.g. ooRexx-5.0.0-11742.centos7.x86_64.rpm . Would it make sense

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

I know, knew, just saying even standards are not standard. ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

Cmake should return “sunOS” From the compiler builtin macro #elif defined(__sun) || defined(sun) # define PLATFORM_ID "SunOS" > On 16 Feb 2019, at 18:40, Jason Martin wrote: > > agrellum@openindiana:~$ uname -v > illumos-c78b1a4529 > > Not OpenIndiana and Not SunOS > > > > > __

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

agrellum@openindiana:~$ uname -v illumos-c78b1a4529 Not OpenIndiana and Not SunOS ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

> Should maybe "PARSE SOURCE" return "UBUNTU" instead of "LINUX" to indicate > that it behaves > differently compared to other Linuxes? Parse source return the info provides by CMAKE_SYSTEM_NAME And by some tweak of configure.ac before that I just run a cmake --system-information info.txt But

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

What would you suggest/advise given your huge knowledge and experiences on so many different Unix systems? Should the test be adapted to check whether Ubuntu is the host system (e.g. "if sysVersion()~caselessPos('Ubuntu')>0 then ...")? Should the function work differently on Ubuntu to match the

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

I started a bit earlier ( do You remember Slackware ) After that I went for Red Hat And got used to the red-hat and friends terminology I can agree on the Debian ways But Ubuntu has taken things a bit too far Apart being too much much windowish for my taste ;-) This morning it took me just

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

Enrico Sorichetti via Oorexx-devel wrote: Unfortunately Ubuntu is well known also for its odd way of doing things haha... The Debian / Ubuntu way makes sense, the other distros are the odd ones! ;-) Seriously... I started out with Red Hat 5.2 back in probably 1999. Yuck. SuSE, Mandrake... m

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766 and testsuite at r11767

You should be more open minded and Spend more time to learn about the different Linux distributions behaviour I spent a couple of hours installing one more Linux distribution I choose Debian, much more trustworthy as a high lever developer platform … And guess what ??? Executing /home/vagran

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

Unfortunately Ubuntu is well known also for its odd way of doing things > On 16 Feb 2019, at 12:55, Rick McGuire wrote: > > It is Unbuntu's though. ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

It is Unbuntu's though. Rick On Sat, Feb 16, 2019 at 6:54 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > Well… that’ not Fedora Linux opinion > > > Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 16 Feb 2019 > OS Name:LINUX > SysVersion:

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

Well… that’ not Fedora Linux opinion Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 16 Feb 2019 OS Name:LINUX SysVersion: Linux 4.20.7-200.fc29.x86_64 Tests ran: 22641 Assertions: 377418 Failures: 1 Errors: 0 [failure] [20190216

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

It's not so simple. That test works as expected on Linux, it looks like it is only failing on Darwin. Rick On Sat, Feb 16, 2019 at 6:38 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > Certainly different from windows , > > On unix it behaves according to the

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

Certainly different from windows , On unix it behaves according to the docs deleteFile uses unlink which does not check the permissions on the file E Quoting the libc manual 14.6 Deleting Files <> <> <>You can delete a file with unlink or remove. Deletion actually deletes a file name. If

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

No, those are correct. The test is expecting that an attempt to delete a read-only file will fail. Just another one of those maddening differences between platforms. Rick On Sat, Feb 16, 2019 at 4:02 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > > Seems to

Re: [Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11766

Seems to work, But It looks like [failure] [20190216 09:49:03.638306] svn:r11734 Change date: 2019-02-08 15:41:41 -0500 Test: TEST_FILE_EXISTS Class: SysFileXXX.testgroup File: /Users/enrico/ooRexx.testSuite/.../base/rexxutil/SysFileXXX.testGroup Line: 116 Failed: asser

[Oorexx-devel] Testing Open Object Rexx Version 5.0.0 r11765

[enrico@enrico-imac ooRexx.testSuite]$rexx -v Open Object Rexx Version 5.0.0 r11765 Build date: Feb 16 2019 Addressing mode: 64 Copyright (c) 1995, 2004 IBM Corporation. All rights reserved. Copyright (c) 2005-2019 Rexx Language Association. All rights reserved. This program and the accompanying m

Re: [Oorexx-devel] Testing the secirty manager message REQUIRES on ooRexx 3.2, 4.2 and 5.0beta

On 06.07.2017 15:33, Rony G. Flatscher wrote: > > Hi there, > > in the past days I have come up with a testGroup to test the ooRexx security > manager in a way such > that the tests can be run under ooRexx 3.2, 4.x and 5.0beta, cf. > , where also the

[Oorexx-devel] Testing the secirty manager message REQUIRES on ooRexx 3.2, 4.2 and 5.0beta

Hi there, in the past days I have come up with a testGroup to test the ooRexx security manager in a way such that the tests can be run under ooRexx 3.2, 4.x and 5.0beta, cf. , where also the output of running the testGroup on all three ooRexx versio

Re: [Oorexx-devel] Testing - second step

Thanks Rick, that works. On 6 October 2014 15:24, Rick McGuire wrote: > Don't bother adding the directives directory or any other directory you're > running tests from to your path. That shouldn't be necessary. You can run > any of the tests by either CDing to the directory or directly by spe

Re: [Oorexx-devel] Testing - second step

Don't bother adding the directives directory or any other directory you're running tests from to your path. That shouldn't be necessary. You can run any of the tests by either CDing to the directory or directly by specifying the full directory name on the rexx command. The directory you DO need

Re: [Oorexx-devel] Testing - second step

Now I am struggling with this. I have added the test trunk base and the directives test folder to my enormous path C:\evolution\oorexx>path > PATH=C:\Program Files\ImageMagick;c:\program > files\imagemagick;C:\Windows\system > > 32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsP

Re: [Oorexx-devel] Testing - second step

on my way How can I test that Novalue is recognized here: ::method "test_3" str='ABC' self~assertSame(str[A],'C') it´s this the best way? ::method "test_3" Signal On Novalue self~expectSyntax(16.1) self~assertSame(str[A],'C') Can I establish Novalue globally?? Walter Pachl -

Re: [Oorexx-devel] Testing - second step

+1 working Von: Rick McGuire [mailto:object.r...@gmail.com] Gesendet: Montag, 06. Oktober 2014 11:39 An: Open Object Rexx Developer Mailing List Betreff: Re: [Oorexx-devel] Testing - second step Jon, For people developing test cases, I really recommend not executing this by running

Re: [Oorexx-devel] Testing - second step

That’s the better answer (I was going to ask Jon :)) Thanks and trying soon Walter Von: Rick McGuire [mailto:object.r...@gmail.com] Gesendet: Montag, 06. Oktober 2014 11:39 An: Open Object Rexx Developer Mailing List Betreff: Re: [Oorexx-devel] Testing - second step Jon, For people

Re: [Oorexx-devel] Testing - second step

Jon, For people developing test cases, I really recommend not executing this by running the entire test suite. I don't want to have to deal with other failures or problems they might turn up. Running the test suite is NOT necessary. For me, all I do is add the root of the test tree and the fram

Re: [Oorexx-devel] Testing - second step

Hi Walter, you will find the answers in Marks document Where you should differ from what Mark wrote is to download the snapshot from SVN using the link Rick gave (which is what you appear to have done) Save it in a folde

[Oorexx-devel] Testing - second step

I do have now d:\_OOTest\trunk containing the entire test suite (downloaded using SVN) d:\_OOTest\Walter.rex (a first little test group) Where (else) should I store this program and how should I invoke it? Any path or classpath adaptations required? Rgds Walter > --

Re: [Oorexx-devel] Testing new SysFileTree?

Michael, Thanks a lot for testing this, I really appreciate it. -- Mark Miesfeld On Sun, Aug 26, 2012 at 5:30 PM, Michael Lueck wrote: > hakan wrote: >> Michel try the Debian build, from buildmachine, usally it works for me on >> Ubuntu >> /hex > > $ sudo dpkg -i oorexx_4.2.0-8276-debian605_i3

Re: [Oorexx-devel] Testing new SysFileTree?

hakan wrote: > Michel try the Debian build, from buildmachine, usally it works for me on > Ubuntu > /hex $ sudo dpkg -i oorexx_4.2.0-8276-debian605_i386.deb Selecting previously deselected package oorexx. (Reading database ... 35848 files and directories currently installed.) Unpacking oorexx (fr

Re: [Oorexx-devel] Testing new SysFileTree?

Michel try the Debian build, from buildmachine, usally it works for me on Ubuntu /hex - Ursprungligt Meddelande: Från: Mark Miesfeld Till: Open Object Rexx Developer Mailing List Kopia: Datum: fredag, 24 augusti 2012 04:45 Ämne: Re: [Oorexx-devel] Testing new

Re: [Oorexx-devel] Testing new SysFileTree?

Hi Michael, I can build a package on a lower version of Ubuntu, but probably not until the weekend. I'll e-mail you directly on how to get the package. Jog my memory here, if you don't see an e-mail from me by Sunday. That's an odd error by the way, I would have expected a crash not an incorre

Re: [Oorexx-devel] Testing new SysFileTree?

Michael Lueck wrote: > I will test with 4.1.1 to make sure SysFileTree crashes, and then try with > the latest build... and report findings. mdlueck@ldslnx01:~$ rexx -v Open Object Rexx Version 4.1.0 Build date: Dec 3 2010 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright

Re: [Oorexx-devel] Testing new SysFileTree?

Greetings Mark, Mark Miesfeld wrote: > You should be able to down load a build from the build machine to test with: > > http://build.oorexx.org/builds/interpreter-main/8244/ > > or pick a later build by going up one directory I will test with 4.1.1 to make sure SysFileTree crashes, and then try w

Re: [Oorexx-devel] Testing new SysFileTree?

On Thu, Aug 23, 2012 at 5:18 PM, Michael Lueck wrote: > I see new packages: > http://sourceforge.net/projects/oorexx/files/oorexx/4.1.2%20%28beta%29/ > > Do those happen to include the updated SysFileTree? I have an Ubuntu Server > 10.04 x86 that had a mountain of extra files on it presently. Mi

[Oorexx-devel] Testing new SysFileTree?

Greetings, I see new packages: http://sourceforge.net/projects/oorexx/files/oorexx/4.1.2%20%28beta%29/ Do those happen to include the updated SysFileTree? I have an Ubuntu Server 10.04 x86 that had a mountain of extra files on it presently. Might give the new code a good workout. I run Ubuntu

Re: [Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

Backing out that change is NOT the correct solution. The new behavior of CSELF is to search up the inheritance chain, allowing subclasses to access a CSELF variable set by a superclass method. This is assuming that the CSELF value will be set by one of the base classes and used by the subclasses.

Re: [Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

David I can get the tests working (under winXP) by doing that : 1) [temporary] Cancel the change done in RexxNativeActivation.cpp rev:5103 old return receiver->getCSelf(); new return receiver->getCSelf(((RexxMethod *)executable)->getScope()); By restoring the old behaviour

Re: [Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

I have tried to debug this unsuccessfully. The problem is in the startup code for the shared library. For some reason the initial startup API for GTK is failing and that causes all subsequent GTK API calls to fail. Something has changed about GTK but I have not been able to locate the problem.

Re: [Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

thanks Rony, I will study these informations ! Jean-Louis -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent

Re: [Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

On 27.11.2011 10:28, Jean-Louis Faucher wrote: > After thoughts, I think this part of my previous mail is not so obvious : > "Obviously, the overwritting should not happen." > > If declaring CSELF is like doing expose CSELF, then it's normal to have a > specific value at each > scope. > Exposed

Re: [Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

After thoughts, I think this part of my previous mail is not so obvious : "Obviously, the overwritting should not happen." If declaring CSELF is like doing expose CSELF, then it's normal to have a specific value at each scope. Exposed variables are not inherited, so the assignment of DictWidget se

Re: [Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

1,5 year later... I installed a more recent distribution of GTK (the all-in-one bundle from http://www.gtk.org/download/win32.php), made a rebuild and still get the same problem. window = .GTKWindow~new(.gtk~GTK_WINDOW_TOPLEVEL) window~show() CSELF is null when executing the native method GrxWidg

Re: [Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

Very strange. This has just started with the recent fixes to GTK applied by Fedora on my system. It worked fine until recently. Still trying to figure out what has changed but this may be a GTK bug. David Ashley On 05/14/2010 01:37 PM, Jean-Louis Faucher wrote: I'm testing RexxGtk and I get a

[Oorexx-devel] Testing RexxGtk : I have an assert error with test2-1.rex

I'm testing RexxGtk and I get an assert error in test2-1.rex. Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed David, is it working for you ? Maybe I'm totally wrong, but it seems that the CSELF assignment should be moved to GtkWidget. When debugging "show", I see that

Re: [Oorexx-devel] Testing front-end API code.

There are a couple of unanswered questions on the list, this is one of the them. On Tue, Sep 16, 2008 at 7:33 AM, Rick McGuire <[EMAIL PROTECTED]> wrote: > API testing is moving along pretty good for the APIs where the tests > can/need to be driven from ooRexx code. There are a lot of tests, > h

Re: [Oorexx-devel] Testing

Sorry folks, have no idea why I included that message in my reply. Lee Lee Peedin wrote: > I see/saw it Rick. > > On top of everything else going on, just got word that my best friend and > fishing partner had a > fatal heart attack this afternoon. > > Lee > > Rick McGuire wrote: >> Just che

Re: [Oorexx-devel] Testing

I see/saw it Rick. On top of everything else going on, just got word that my best friend and fishing partner had a fatal heart attack this afternoon. Lee Rick McGuire wrote: > Just checking to see if the mailing list problems are fixeddoes > anybody see this? > > Rick > > ---

[Oorexx-devel] Testing

Just checking to see if the mailing list problems are fixeddoes anybody see this? Rick - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin

[Oorexx-devel] Testing front-end API code.

API testing is moving along pretty good for the APIs where the tests can/need to be driven from ooRexx code. There are a lot of tests, however, that test creation of interpreter instances and the various upfront bits such as enabling exits, etc. I can see two basic approaches to this: 1) create