Re: [Oorexx-devel] sourceforge down

2017-02-22 Thread Rony G. Flatscher 
On 21.02.2017 19:04, Chip Davis wrote:
> It appears that Rony works so hard, he's vaulted himself more than a 
> week ahead of the rest of us.  :-))
8)

[Well, the last weeks were a little bit ... exhaustive, 7 days, 12-14 hours...]

>
> On 2/21/2017 3:35 AM, René Jansen wrote:
>> Thanks Rony. I should have opened a ticket also, all the usual
>> channels were silent. Will set up a shadow for NetRexx.
>>
>>> On 20 Feb 2017, at 22:14, Rony wrote:
>>> Today I opened a ticket with Sourceforge:
>>>
>>> All of a sudden svn (update/ci) not working on projects oorexx, bsf4oorexx,
>>> netrexx since *2017-02-26* !!


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] Tuesday (Re: Now thread about debugging this

2017-02-22 Thread Rony G. Flatscher 
Went again thru the BSF4ooRexx code. Have not found anything, however a few 
observations:

  * When doing a RequestGlobalReference() on the argument array *and* its sole 
entry, then the
program ran to the end without a problem.
  * Adding additional output statements (that also caused more 
call-to-Java-to-Rexx, calls to
SendMessage0() and CString()) caused the exception again. However much 
further towards the end
of the test Rexx program.

This is the message scenario in this case:

RII=Rexx Interpreter Instance RII #1 RII # 2 BSF.CLS BSF4ooRexx.cc Java 
(Host.rex)
(test_set_.rex) |->|>|--->| |
|<--|< run test_set_.rex |
|-->|--->| | 
|<|<--->|<-->| |
|<->|<-->| ... and so on ... |
|<|<|<---| | 
|-->|--->| |
|<--|<---| | 
|>|>|--->| ... and
so on ... | |--->| (end test_set_.rex)
|<---|<---| (end Host.rex)

  * Everything is carried out in the same thread.
  * "test_set.rex" causes a lot of calls to Java (via BSF.CLS) which may cause 
a lot of calls back
into Rexx. (In this application a majority of the callbacks from Java are 
related to appending
entries into Rexx array objects from Java.)

Today I would be able to help debug this in the next 30 minutes, then after a 
meeting which ends in
about two hours, I would be able to work on this for three hours, and then 
after a dinner meeting
(ending in 8 hours) I could work a couple of hours again on this.

So any hints, ideas what I could do highly appreciated! Again, please bear with 
me, I still have to
get acquainted with debugging using a GUI! :)

---rony


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] Question ad GetAllContextVariables()

2017-02-22 Thread Rony G. Flatscher 
While going thru the code I "stumbled" over the "excessive" use of 
GetAllContextVariables().

There is an external Rexx function in BSF4ooRexx that uses that API and 
immediately returns the
directory it gets from GetAllContextVariables(). So I was wondering, whether it 
makes sense to look
into that corner w.r.t. problem that the test script triggers, and if so, where?

---rony




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question ad GetAllContextVariables()

2017-02-22 Thread Rick McGuire 
I doubt that would be the source of the problem, but you do realize you can
retrieve the context variables without calling an external function?

Rick

On Wed, Feb 22, 2017 at 6:33 AM, Rony G. Flatscher 
wrote:

> While going thru the code I "stumbled" over the "excessive" use of
> GetAllContextVariables().
>
> There is an external Rexx function in BSF4ooRexx that uses that API and
> immediately returns the
> directory it gets from GetAllContextVariables(). So I was wondering,
> whether it makes sense to look
> into that corner w.r.t. problem that the test script triggers, and if so,
> where?
>
> ---rony
>
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question ad GetAllContextVariables()

2017-02-22 Thread Rony G. Flatscher 
On 22.02.2017 12:38, Rick McGuire wrote:
> I doubt that would be the source of the problem, but you do realize you can 
> retrieve the context
> variables without calling an external function?
Yes, via .context~variables. In this case (for orthogonality) the external Rexx 
function
BSFContextVariable() allows for getting (all, individual), setting (all, 
individual) and deleting
context variables.

In the Rexx script usage scenario this gets exploited to incorporate 
javax.script.ScriptContext
attributes from the host as local Rexx variables. That is the purpose of the 
injected code. (The
programmer has to list the desired attributes in a Rexx block comment that 
contains a @get() or
@set() annotation. This way the Rexx programmer can easily determine and 
interface with the external
attributes. This also is supposed to inhibit the unnoticed overwriting of local 
Rexx variables with
ScriptContext attributes, if one would automatically incorporate those 
attributes automaticalls.)

---rony

>
>
> On Wed, Feb 22, 2017 at 6:33 AM, Rony G. Flatscher  > wrote:
>
> While going thru the code I "stumbled" over the "excessive" use of 
> GetAllContextVariables().
>
> There is an external Rexx function in BSF4ooRexx that uses that API and 
> immediately returns the
> directory it gets from GetAllContextVariables(). So I was wondering, 
> whether it makes sense to
> look
> into that corner w.r.t. problem that the test script triggers, and if so, 
> where?
>
> ---rony
>

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] LinuxOne build up and running again

2017-02-22 Thread René Jansen 
Things with IBM did not work out (I was trying to get a non-expiring small 
business VM with Linux (SLES) on Z) (they stopped answering).

But:

I am happy to announce that the ooRexx for Linux on Z is up and running again 
due to a gracious donation of ICU-IT.NL, which has granted RexxLA use of a SLES 
on their LinuxONE mainframe, for the purpose of building and testing Open 
Object Rexx. It is accessible through the build machine at 
http://build.oorexx.org  .

I see that a few testcases fail, so there is work to do.

best regards,

René.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] Question about ooRexx Linux build machine

2017-02-22 Thread Michael Lueck 
Greetings,

So I believe the current "ooRexx build machine" is said to utilize Jenkins. Is 
that correct?

So how does one go about setting up instances of various distros (Ubuntu) on 
it? Is it some sort of a virtual machine server that you can install your 
distro into, then have it run a build upon the OS 
installed?

I would like to take the time to get the Ubuntu builds for LTS releases in 
shape.

Once successfully accomplished... I would then consider on supporting the 
latest Debian. I recall that in the past there were issues running the Ubuntu 
build on Debian, or vise versa.

I am thankful,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Tuesday (Re: Now thread about debugging this

2017-02-22 Thread Rony G. Flatscher 
OK, in the meantime I updated ooRexx 5.0 to the current trunk version and 
rebuilt the debug version
(still have problems with oodialog, which cannot be built as I reported a few 
days ago).

There are two different stack traces that I am able to get repeatedly (one 
calling a Rexx program
externally, the other one using .context~package~addPackage), if that helps.

Stack trace if calling a Rexx program externally from Rexx code in BSF.CLS:

Register to memory mapping: EAX=0x4453 is an unknown value EBX={method} 
{0x1524e94c}
'jniRexxSendMessageToRexxObject'

'(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Ljava/lang/Object;Ljava/lang/String;)Ljava/lang/Object;'
in 'org/rexxla/bsf/engines/rexx/RexxAndJava' ECX=0x4453 is an unknown 
value EDX=0x
is an unknown value ESP=0x0031c3d0 is pointing into the stack for thread: 
0x02bbd400
EBP=0x0031c3d8 is pointing into the stack for thread: 0x02bbd400 
ESI=0x0031c40c is pointing into
the stack for thread: 0x02bbd400 EDI=0x0031c55c is pointing into the stack 
for thread:
0x02bbd400 Stack: [0x002a,0x0032], sp=0x0031c3d0, free space=496k 
Native frames:
(J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C 
[rexx.dll+0x2338a]
ObjectHeader::isObjectMarked+0x1a C [rexx.dll+0x233dd] 
RexxInternalObject::isObjectMarked+0x1d C
[rexx.dll+0xa6bba] RexxActivation::live+0x61a C [rexx.dll+0xd9eef]
MemoryObject::markObjectsMain+0xcf C [rexx.dll+0xd9db7] 
MemoryObject::markObjects+0x27 C
[rexx.dll+0xda111] MemoryObject::collect+0x61 C [rexx.dll+0xcb5ad]
LargeSegmentSet::expandOrCollect+0xad C [rexx.dll+0xcb303]
LargeSegmentSet::handleAllocationFailure+0x23 C [rexx.dll+0xd95af] 
MemoryObject::newObject+0xbf
C [rexx.dll+0x23c85] new_object+0x15 C [rexx.dll+0x250f1] 
BufferClass::operator new+0x11 C
[rexx.dll+0x2561f] new_buffer+0x1f C [rexx.dll+0x135a60] 
SystemInterpreter::readProgram+0xc0 C
[rexx.dll+0x12c893] LanguageParser::createProgramFromFile+0x53 C 
[rexx.dll+0xa98fe]
RexxActivation::callExternalRexx+0xae C [rexx.dll+0x133f8f]
SystemInterpreter::invokeExternalFunction+0x6f C [rexx.dll+0xa9bb6]
RexxActivation::externalCall+0x146 C [rexx.dll+0x100262] 
RexxInstructionCall::execute+0x132 C
[rexx.dll+0xa7c1e] RexxActivation::run+0x39e C [rexx.dll+0xb5188] 
RexxCode::run+0x58 C
[rexx.dll+0x35e23] MethodClass::run+0x43 C [rexx.dll+0x4b2fc] 
RexxObject::messageSend+0xcc C
[rexx.dll+0xfabbc] ExpressionStack::send+0x3c C [rexx.dll+0x10c2a6]
RexxInstructionMessage::execute+0x136 C [rexx.dll+0xa7c1e] 
RexxActivation::run+0x39e C
[rexx.dll+0xb520a] RexxCode::call+0x6a C [rexx.dll+0xb5264] 
RexxCode::call+0x44 C
[rexx.dll+0x599a6] RoutineClass::callWithRexx+0xa6 C [rexx.dll+0xa4ad4] 
CPPCode::run+0x154 C
[rexx.dll+0x35e23] MethodClass::run+0x43 C [rexx.dll+0x4b2fc] 
RexxObject::messageSend+0xcc C
[rexx.dll+0x4b6a0] RexxObject::sendMessage+0x30 C [rexx.dll+0x831ee] 
SendMessageArray+0x8e C
[BSF4ooRexx.DLL+0x15872] RexxThreadContext_::SendMessageA+0x22 C 
[BSF4ooRexx.DLL+0x9cd6]

Java_org_rexxla_bsf_engines_rexx_RexxAndJava_jniRexxSendMessageToRexxObject+0x566
 j

org.rexxla.bsf.engines.rexx.RexxAndJava.jniRexxSendMessageToRexxObject(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Ljava/lang/Object;Ljava/lang/String;)Ljava/lang/Object;+0
j

org.rexxla.bsf.engines.rexx.RexxEngine.call(Ljava/lang/Object;Ljava/lang/String;[Ljava/lang/Object;)Ljava/lang/Object;+235
j

org.rexxla.bsf.engines.rexx.RexxProxy.sendMessage1(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/Object;+59
j

org.rexxla.bsf.engines.rexx.jsr223.RexxCompiledScript.eval(Ljavax/script/ScriptContext;)Ljava/lang/Object;+127
j

org.rexxla.bsf.engines.rexx.jsr223.RexxScriptEngine.eval(Ljava/lang/String;Ljavax/script/ScriptContext;)Ljava/lang/Object;+139
j

org.rexxla.bsf.engines.rexx.jsr223.RexxScriptEngine.eval(Ljava/io/Reader;Ljavax/script/ScriptContext;)Ljava/lang/Object;+20
v ~StubRoutines::call_stub V [jvm.DLL+0x15aa85] V [jvm.DLL+0x220d7e] V 
[jvm.DLL+0x15ab1e] V
[jvm.DLL+0x1672c8] V [jvm.DLL+0x167533] V [jvm.DLL+0x103f33] C 
[java.dll+0x3b26] j

sun.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+100
j

sun.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+6
j 
java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+56
 j

org.rexxla.bsf.engines.rexx.RexxAndJava.invokeMethod(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+3
j

org.rexxla.bsf.engines.rexx.RexxAndJava.javaCallBSF([Ljava/lang/String;)Ljava/lang/String;+5859
v ~StubRoutines::call_stub V [jvm.DLL+0x1

[Oorexx-devel] Another, maybe interesting observation

2017-02-22 Thread Rony G. Flatscher 
O.K., this may be a little bit weird: I can manage to have the test code run 
without an exception,
repeatedly!

Background: in the native code I have many, many output statements to stderr 
for debugging (tons
over the years, controlled by defines) in the form of, e.g:

fprintf(stderr, "...\t\t\t\t\targ(%d)=[%s]\n", idx,
rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
fflush(stderr);

Changing the above output to:

fprintf(stderr, "...\t\t\t\t\targ(%d)=[%*.64*s]\n", idx,
rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
fflush(stderr);

makes the test code run it seems!

Without restricting the output to a maximum of 64 bytes causes variable long 
strings, including the
source code of executed Rexx scripts to be displayed. The longest such 
displayed string is around
6.6 KB large. It is then that I receive the exceptions as if the 
fprintf-statement (or the
formatting of the string to output) overlays some Rexx memory causing 
eventually that exception.
Could that be possible?

---rony

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Another, maybe interesting observation

2017-02-22 Thread Rick McGuire 
On Wed, Feb 22, 2017 at 9:33 AM, Rony G. Flatscher 
wrote:

> O.K., this may be a little bit weird: I can manage to have the test code
> run without an exception, repeatedly!
> Background: in the native code I have many, many output statements to
> stderr for debugging (tons over the years, controlled by defines) in the
> form of, e.g:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%s]\n", idx, 
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
> fflush(stderr);
>
> Changing the above output to:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%*.64*s]\n", idx, 
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
> fflush(stderr);
>
> makes the test code run it seems!
>
> Without restricting the output to a maximum of 64 bytes causes variable
> long strings, including the source code of executed Rexx scripts to be
> displayed. The longest such displayed string is around 6.6 KB large. It is
> then that I receive the exceptions as if the fprintf-statement (or the
> formatting of the string to output) overlays some Rexx memory causing
> eventually that exception. Could that be possible?
>

A memory overwrite was suggested as a possibility in every one of them, so
yeah, this could be what was happening.

Rick

>
>
> ---rony
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Another, maybe interesting observation

2017-02-22 Thread Rony G. Flatscher 
On 22.02.2017 15:40, Rick McGuire wrote:
>
>
> On Wed, Feb 22, 2017 at 9:33 AM, Rony G. Flatscher  > wrote:
>
> O.K., this may be a little bit weird: I can manage to have the test code 
> run without an
> exception, repeatedly!
>
> Background: in the native code I have many, many output statements to 
> stderr for debugging
> (tons over the years, controlled by defines) in the form of, e.g:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%s]\n", idx,
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
> fflush(stderr);
>
> Changing the above output to:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%*.64*s]\n", idx,
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
> fflush(stderr);
>
> makes the test code run it seems! Without restricting the output to a 
> maximum of 64 bytes
> causes variable long strings, including the source code of executed Rexx 
> scripts to be
> displayed. The longest such displayed string is around 6.6 KB large. It 
> is then that I receive
> the exceptions as if the fprintf-statement (or the formatting of the 
> string to output)
> overlays some Rexx memory causing eventually that exception. Could that 
> be possible?
>
> A memory overwrite was suggested as a possibility in every one of them, so 
> yeah, this could be
> what was happening. 
Played around a little bit and added output statements in Java to "System.err" 
and now I get
exceptions again. Is there anything I could do to prevent this? ---rony
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Another, maybe interesting observation

2017-02-22 Thread Rick McGuire 
On Wed, Feb 22, 2017 at 9:33 AM, Rony G. Flatscher 
wrote:

> O.K., this may be a little bit weird: I can manage to have the test code
> run without an exception, repeatedly!
> Background: in the native code I have many, many output statements to
> stderr for debugging (tons over the years, controlled by defines) in the
> form of, e.g:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%s]\n", idx, 
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
> fflush(stderr);
>
> Changing the above output to:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%*.64*s]\n", idx, 
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
> fflush(stderr);
>
> makes the test code run it seems!
>

btw, thjis is also going to add two entries to the local reference table
each time you do this. The table could end up getting quite large if you
have a long running call. If you're only doing this for debug purposes, it
probably doesn't matter.

Rick


>
> Without restricting the output to a maximum of 64 bytes causes variable
> long strings, including the source code of executed Rexx scripts to be
> displayed. The longest such displayed string is around 6.6 KB large. It is
> then that I receive the exceptions as if the fprintf-statement (or the
> formatting of the string to output) overlays some Rexx memory causing
> eventually that exception. Could that be possible?
>
> ---rony
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Another, maybe interesting observation

2017-02-22 Thread Rony G. Flatscher 

On 22.02.2017 15:44, Rick McGuire wrote:
>
>
> On Wed, Feb 22, 2017 at 9:33 AM, Rony G. Flatscher  > wrote:
>
> O.K., this may be a little bit weird: I can manage to have the test code 
> run without an
> exception, repeatedly!
>
> Background: in the native code I have many, many output statements to 
> stderr for debugging
> (tons over the years, controlled by defines) in the form of, e.g:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%s]\n", idx,
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
> fflush(stderr);
>
> Changing the above output to:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%*.64*s]\n", idx,
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
> fflush(stderr);
>
> makes the test code run it seems! 
>
> btw, thjis is also going to add two entries to the local reference table each 
> time you do this.
> The table could end up getting quite large if you have a long running call. 
> If you're only doing
> this for debug purposes, it probably doesn't matter. 
Yes, it is for debugging only. ---rony
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] LinuxOne build up and running again

2017-02-22 Thread Erich Steinböck 
>
> SLES on their LinuxONE mainframe .. accessible through the build machine
> at http://build.oorexx.org .
>
René, very good news!  Thanks!

I see that a few testcases fail, so there is work to do.
>
The failing test cases have already been fixed yesterday.  I just re-ran
the tests on the Z slave, and lights are green!
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question about ooRexx Linux build machine

2017-02-22 Thread Erich Steinböck 
>
> the current "ooRexx build machine" is said to utilize Jenkins. Is that
> correct?
>
Yes

how does one go about setting up instances of various distros (Ubuntu) on
> it?
> Is it some sort of a virtual machine server that you can install your
> distro into,
> then have it run a build upon the OS installed?
>
Jenkins is a dispatcher only.  It dispatches jobs to any number of slave
machines.  You'll have to set up a slave (typically a VM that you have
access to), which can build and test ooRexx.  If this works, you can tell
the Jenkins build server about it, and have it schedule automatic builds.

I've done above on a Ubuntu 16.04 VM, and have successfully added it to our
Jenkins build server.  Any repository changes will now automatically
trigger a build, a test, and a copy of the resulting install image to the
ooRexx sourceforge files section for anyone to download.

René will have to set a Jenkins build server account for you, and I'd be
more than willing to help with any questions you have.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Another, maybe interesting observation

2017-02-22 Thread Rony G. Flatscher 
Is there anything I could do to provide information that could help solve this 
problem, or is enough
already known?

---rony


On 22.02.2017 15:48, Rony G. Flatscher wrote:
>
> On 22.02.2017 15:44, Rick McGuire wrote:
>>
>>
>> On Wed, Feb 22, 2017 at 9:33 AM, Rony G. Flatscher > > wrote:
>>
>> O.K., this may be a little bit weird: I can manage to have the test code 
>> run without an
>> exception, repeatedly!
>>
>> Background: in the native code I have many, many output statements to 
>> stderr for debugging
>> (tons over the years, controlled by defines) in the form of, e.g:
>>
>> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%s]\n", idx,
>> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
>> fflush(stderr);
>>
>> Changing the above output to:
>>
>> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%*.64*s]\n", idx,
>> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING"))); 
>> fflush(stderr);
>>
>> makes the test code run it seems! 
>>
>> btw, thjis is also going to add two entries to the local reference table 
>> each time you do this.
>> The table could end up getting quite large if you have a long running call. 
>> If you're only doing
>> this for debug purposes, it probably doesn't matter. 
> Yes, it is for debugging only. ---rony 
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question about ooRexx Linux build machine

2017-02-22 Thread Michael Lueck 
Greetings Erich,

Erich Steinböck wrote:
> Jenkins is a dispatcher only.  It dispatches jobs to any number of slave 
> machines.  You'll have to set up a slave


O, that makes more sense.

I thought there was some ooRexx VM server that David used to run. Did that end 
up going away? David was going to teach me and that never happened.

So I best just do my own thing in VirtualBox on my own system?


Erich Steinböck wrote:
> I've done above on a Ubuntu 16.04 VM


Excellent.

I am thankful,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question about ooRexx Linux build machine

2017-02-22 Thread Erich Steinböck 
>
> I thought there was some ooRexx VM server that David used to run. Did that
> end up going away?
>
When David left as ooRexx dev, he took the box with him to his new Redhat
engagement

So I best just do my own thing in VirtualBox on my own system?
>
Even if you machine isn't online 24x7, it may still be worth to set it up
as a Jenkins slave.  I think we already have a few slaves with limited
availability.

There were rumors some time ago that we might be able to get hold of a VM
on Amazon's EC2, but unfortunately that never happened.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel