Re: [Oorexx-devel] Jenkins

[ooRexx]

Hi Erich, thanks for letting me know. I will keep it running. It is very small 
so no problem to keep.

FYI I have now upgraded my Mac where the VMs run from Catalina (macOS 10.15) to 
Sonoma (macOS 14.5). Also Virtualbox was upgraded to the latest version. All 
went well and everything works except a scanner that stopped scanning pdfs. I 
will move to Sequoia (macOS 15) once it is stable.

Contrary to my expectations I could not make VMs of Ventura (macOS 13) or 
Sonoma (macOS 14) so I am building macOS on native Sonoma, we now have one 
macOS dmg installer for Intel (x86_64) and one for M1 Mac for the latest macOS 
and, ofcourse, the universal zip installer.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> On 8. Jul 2024, at 09:51, Erich Steinböck  wrote:
> 
>> anyone has an idea of how to get Java 17 (or higher) on to Solaris
> Hi P.O.,
> I, too, think Solaris does not support Java 17 or later.
> You might still want to keep the VM so in an emergency we could manually 
> build and test on Solaris 11.
> ___
> 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

Re: [Oorexx-devel] Jenkins

[Erich Steinböck]

>
> anyone has an idea of how to get Java 17 (or higher) on to Solaris
>
Hi P.O.,
I, too, think Solaris does not support Java 17 or later.
You might still want to keep the VM so in an emergency we could manually
build and test on Solaris 11.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[ooRexx]

So I could finally get all the agents to Java 17, with one exception - I could 
not find support for Solaris 11 which is weird since it is an Oracle product.

Contrary to my original understanding of the (mandatory) migration to Java 17, 
the Agents must run Java 17 or higher, not lower, as I had understood it.

I have no solution for bringing Solaris 11 back online again, if anyone has an 
idea of how to get Java 17 (or higher) on to Solaris s/he is welcome to provide 
a solution, otherwise I will detach Solaris from the build machine.

FYI On OpenIndiana (another descendant of Sun OS) I could get Java 17, since it 
was already part of the installation.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> On 29. Jun 2024, at 18:57, René Jansen  wrote:
> 
> Hi P.O.,
> 
> Let us know when it is finished … so we can all have a look.
> 
> Best regards,
> 
> René.
> 
>> On 29 Jun 2024, at 17:50, ooRexx  wrote:
>> 
>> So Jenkins Master is running Java 17 and I have upgraded the Linux/Unix 
>> slaves, will do the Mac and Windows in the coming days, it took a bit longer 
>> than expected. 
>> 
>> Building & testing should work but the Win and Mac platforms will be pending 
>> until I am done with all Agents. sorry but I have limited time right now.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>>> On 28. Jun 2024, at 18:17, ooRexx >> > wrote:
>>> 
>>> I am upgrading Jenkins to Java 17 so Jenkins may be unresponsive. I would 
>>> appreciate if no new commits are done in the coming hours.
>>> 
>>> I will upgrade all the Agents as soon as I can, for now they should work 
>>> with Java 11.
>>> 
>>> The upgrade to Java 17 was mandatory to keep Jenkins running in case you 
>>> wonder why it was done.
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>> 
>>> 
>>> 
>>> ___
>>> 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
> ___
> 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

Re: [Oorexx-devel] Jenkins

[René Jansen]

Hi P.O.,Let us know when it is finished … so we can all have a look.Best regards,René.On 29 Jun 2024, at 17:50, ooRexx  wrote:So Jenkins Master is running Java 17 and I have upgraded the Linux/Unix slaves, will do the Mac and Windows in the coming days, it took a bit longer than expected. Building & testing should work but the Win and Mac platforms will be pending until I am done with all Agents. sorry but I have limited time right now.
Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se

On 28. Jun 2024, at 18:17, ooRexx  wrote:I am upgrading Jenkins to Java 17 so Jenkins may be unresponsive. I would appreciate if no new commits are done in the coming hours.I will upgrade all the Agents as soon as I can, for now they should work with Java 11.The upgrade to Java 17 was mandatory to keep Jenkins running in case you wonder why it was done.
Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se



___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[ooRexx]

So Jenkins Master is running Java 17 and I have upgraded the Linux/Unix slaves, 
will do the Mac and Windows in the coming days, it took a bit longer than 
expected. 

Building & testing should work but the Win and Mac platforms will be pending 
until I am done with all Agents. sorry but I have limited time right now.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> On 28. Jun 2024, at 18:17, ooRexx  wrote:
> 
> I am upgrading Jenkins to Java 17 so Jenkins may be unresponsive. I would 
> appreciate if no new commits are done in the coming hours.
> 
> I will upgrade all the Agents as soon as I can, for now they should work with 
> Java 11.
> 
> The upgrade to Java 17 was mandatory to keep Jenkins running in case you 
> wonder why it was done.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[René Jansen]

Hi P.O.,

ok great - thanks!

best regards,

René

> On 28 Jun 2024, at 18:17, ooRexx  wrote:
> 
> I am upgrading Jenkins to Java 17 so Jenkins may be unresponsive. I would 
> appreciate if no new commits are done in the coming hours.
> 
> I will upgrade all the Agents as soon as I can, for now they should work with 
> Java 11.
> 
> The upgrade to Java 17 was mandatory to keep Jenkins running in case you 
> wonder why it was done.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[Gilbert Barmwater]

OK, great!  Thanks Rony!

On 10/28/2023 9:23 AM, Rony G. Flatscher wrote:

Gil,

On 27.10.2023 17:19, Gilbert Barmwater wrote:
Glad to see that you are back "in the saddle" so to speak!  Rony and 
I have been working off-list to implement a mechanism to automate the 
updating of the information in the "Edition" of each book.  I have 
done the change in the ooRexx version of the documentation build 
tools. Rony has offered a change to handle a Mac-only requirement 
which I have incorporated.  I'm not sure if he had the time to 
actually run the build tools on Mac or if the change he suggested was 
based only on reading the programs and the difficulty he had in using 
the shell scripts.  In any case, once we know that the ooRexx version 
of the tools runs on Mac, I would request that you switch your 
process to those tools and then the revision numbering issue will be 
resolved.  I have the changes to the ooRexx tools ready and will 
probably commit them later today. 


the changes got tested on a Mac.

---rony




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


--
Gil Barmwater



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[Rony G. Flatscher]

Gil,

On 27.10.2023 17:19, Gilbert Barmwater wrote:
Glad to see that you are back "in the saddle" so to speak!  Rony and I have been working off-list 
to implement a mechanism to automate the updating of the information in the "Edition" of each 
book.  I have done the change in the ooRexx version of the documentation build tools.  Rony has 
offered a change to handle a Mac-only requirement which I have incorporated.  I'm not sure if he 
had the time to actually run the build tools on Mac or if the change he suggested was based only 
on reading the programs and the difficulty he had in using the shell scripts.  In any case, once 
we know that the ooRexx version of the tools runs on Mac, I would request that you switch your 
process to those tools and then the revision numbering issue will be resolved.  I have the changes 
to the ooRexx tools ready and will probably commit them later today. 


the changes got tested on a Mac.

---rony




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P. O. Jonsson]

And there is no requirement to use Mac for the documentation build. We could just as well set up a new VM Running Windows, I have spare licenses. Since all Windows platforms run two build and two test jobs I think it would be better to give the Documentation build a separate VM. Von meinem iPhone gesendetAm 27.10.2023 um 17:50 schrieb Gilbert Barmwater :

  

  
  
Hi P.O.,
Glad to see that you are back "in the saddle" so to speak!  Rony
  and I have been working off-list to implement a mechanism to
  automate the updating of the information in the "Edition" of each
  book.  I have done the change in the ooRexx version of the
  documentation build tools.  Rony has offered a change to handle a
  Mac-only requirement which I have incorporated.  I'm not sure if
  he had the time to actually run the build tools on Mac or if the
  change he suggested was based only on reading the programs and the
  difficulty he had in using the shell scripts.  In any case, once
  we know that the ooRexx version of the tools runs on Mac, I would
  request that you switch your process to those tools and then the
  revision numbering issue will be resolved.  I have the changes to
  the ooRexx tools ready and will probably commit them later today.
On 10/27/2023 10:24 AM, ooRexx wrote:


  
  This is just to say that our OpenIndiana VN Agent is
offline due to low Disk space. I tried to extend it but it did
not work so I will have to make a fresh install with more disk
space. Hopefully I can do it this weekend. All other platforms
are online and seems to build & test happily.
  
  
  Also I have moved the building of the documentation
to a VM (macOS Monterey) and it is now working as intended BUT
the changes introduced by Rony for the Revision numbering are
not being picked up. I would need an explanation (again) what I
need to do to make the revision changes become visible in the
documentation. Example todays build of Rexref.pdf
  
  
  ooRexx Documentation 5.1.0 Open Object Rexx
  Reference
  Edition 2023.01.01 (last revised on 20221024 with
r12526
  
  
  I guess this is not what it should say.
  
  
  

  Hälsningar/Regards/Grüsse,
  P.O. Jonsson
  oor...@jonases.se
  
  


  
  
  
  
  
  
  ___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


-- 
Gil Barmwater
  

___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P. O. Jonsson]

Ok I will have to try those tools offline and see how I can merge them with what I have. I have to make sure the uploading works as intended with that toolset. This might not be done just right now but it is in my pipeline. Thanks for responding Von meinem iPhone gesendetAm 27.10.2023 um 17:50 schrieb Gilbert Barmwater :

  

  
  
Hi P.O.,
Glad to see that you are back "in the saddle" so to speak!  Rony
  and I have been working off-list to implement a mechanism to
  automate the updating of the information in the "Edition" of each
  book.  I have done the change in the ooRexx version of the
  documentation build tools.  Rony has offered a change to handle a
  Mac-only requirement which I have incorporated.  I'm not sure if
  he had the time to actually run the build tools on Mac or if the
  change he suggested was based only on reading the programs and the
  difficulty he had in using the shell scripts.  In any case, once
  we know that the ooRexx version of the tools runs on Mac, I would
  request that you switch your process to those tools and then the
  revision numbering issue will be resolved.  I have the changes to
  the ooRexx tools ready and will probably commit them later today.
On 10/27/2023 10:24 AM, ooRexx wrote:


  
  This is just to say that our OpenIndiana VN Agent is
offline due to low Disk space. I tried to extend it but it did
not work so I will have to make a fresh install with more disk
space. Hopefully I can do it this weekend. All other platforms
are online and seems to build & test happily.
  
  
  Also I have moved the building of the documentation
to a VM (macOS Monterey) and it is now working as intended BUT
the changes introduced by Rony for the Revision numbering are
not being picked up. I would need an explanation (again) what I
need to do to make the revision changes become visible in the
documentation. Example todays build of Rexref.pdf
  
  
  ooRexx Documentation 5.1.0 Open Object Rexx
  Reference
  Edition 2023.01.01 (last revised on 20221024 with
r12526
  
  
  I guess this is not what it should say.
  
  
  

  Hälsningar/Regards/Grüsse,
  P.O. Jonsson
  oor...@jonases.se
  
  


  
  
  
  
  
  
  ___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


-- 
Gil Barmwater
  

___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[Gilbert Barmwater]

Hi P.O.,

Glad to see that you are back "in the saddle" so to speak!  Rony and I 
have been working off-list to implement a mechanism to automate the 
updating of the information in the "Edition" of each book.  I have done 
the change in the ooRexx version of the documentation build tools.  Rony 
has offered a change to handle a Mac-only requirement which I have 
incorporated.  I'm not sure if he had the time to actually run the build 
tools on Mac or if the change he suggested was based only on reading the 
programs and the difficulty he had in using the shell scripts.  In any 
case, once we know that the ooRexx version of the tools runs on Mac, I 
would request that you switch your process to those tools and then the 
revision numbering issue will be resolved.  I have the changes to the 
ooRexx tools ready and will probably commit them later today.


On 10/27/2023 10:24 AM, ooRexx wrote:
This is just to say that our OpenIndiana VN Agent is offline due to 
low Disk space. I tried to extend it but it did not work so I will 
have to make a fresh install with more disk space. Hopefully I can do 
it this weekend. All other platforms are online and seems to build & 
test happily.


Also I have moved the building of the documentation to a VM (macOS 
Monterey) and it is now working as intended BUT the changes introduced 
by Rony for the Revision numbering are not being picked up. I would 
need an explanation (again) what I need to do to make the revision 
changes become visible in the documentation. Example todays build of 
Rexref.pdf


ooRexx Documentation 5.1.0 Open Object Rexx
Reference
Edition 2023.01.01 (last revised on 20221024 with r12526

I guess this is not what it should say.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se





___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


--
Gil Barmwater
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

Ok, your call. Once the current changes come through I will add any remaining 
errors/failures to the ticket.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 04.04.2023 um 22:35 schrieb Rick McGuire :
> 
> I have never logged in to Jenkins. Don't really want to. 
> 
> Rick
> 
> On Tue, Apr 4, 2023 at 4:31 PM P.O. Jonsson  > wrote:
> Sorry I was OK, I have made it a bug report to save bandwidth here.
> 
> I assume you can logon to Jenkins? It is much easier to check it out there.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
>> Am 04.04.2023 um 21:04 schrieb Rick McGuire > >:
>> 
>> PO, please post the complete list of files with errors. The fix is correct, 
>> the error is in the test cases. 
>> 
>> Rick
>> 
>> On Tue, Apr 4, 2023 at 2:56 PM P.O. Jonsson > > wrote:
>> All went well and Jenkins is up again. Besides Marks M1 Mac all 
>> platforms are online.
>> 
>> I looked at the current projects and it seems most builds pass but ALL test 
>> fail with the build from 3.4.2023. The build before that. from 1.4.2023 
>> seems to have passed on most platforms.
>> 
>> On CentOS there are 59 Failures and 20 Errors, here some of them
>> 
>> caselessLastpos.testGroup
>> lastpos.testGroup 
>> caselessWordPos.testGroup
>> overlay.testGroup
>> String_verifyMethod.testGroup
>> String_wordposMethod.testGroup
>> String_bitorMethod.testGroup
>> bitxor.testGroup
>> caselessCompare.testGroup
>> 
>> But there are more. Please review the latest commit.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>> 
>>> Am 04.04.2023 um 15:48 schrieb P.O. Jonsson >> >:
>>> 
>>> I am making a 2nd attempt to replace my cable modem/router today and 
>>> tomorrow, so Jenkins may be unavailable for some time.
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> 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 
>> 
>> ___
>> 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 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[Rick McGuire]

I have never logged in to Jenkins. Don't really want to.

Rick

On Tue, Apr 4, 2023 at 4:31 PM P.O. Jonsson  wrote:

> Sorry I was OK, I have made it a bug report to save bandwidth here.
>
> I assume you can logon to Jenkins? It is much easier to check it out there.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
>
> Am 04.04.2023 um 21:04 schrieb Rick McGuire :
>
> PO, please post the complete list of files with errors. The fix is
> correct, the error is in the test cases.
>
> Rick
>
> On Tue, Apr 4, 2023 at 2:56 PM P.O. Jonsson  wrote:
>
>> All went well and Jenkins is up again. Besides Marks M1 Mac all
>> platforms are online.
>>
>> I looked at the current projects and it seems most builds pass but ALL
>> test fail with the build from 3.4.2023. The build before that. from
>> 1.4.2023 seems to have passed on most platforms.
>>
>> On CentOS there are 59 Failures and 20 Errors, here some of them
>>
>> caselessLastpos.testGroup
>> lastpos.testGroup
>> caselessWordPos.testGroup
>> overlay.testGroup
>> String_verifyMethod.testGroup
>> String_wordposMethod.testGroup
>> String_bitorMethod.testGroup
>> bitxor.testGroup
>> caselessCompare.testGroup
>>
>> But there are more. Please review the latest commit.
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>>
>>
>>
>>
>> Am 04.04.2023 um 15:48 schrieb P.O. Jonsson :
>>
>> I am making a 2nd attempt to replace my cable modem/router today and
>> tomorrow, so Jenkins may be unavailable for some time.
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>>
>>
>>
>>
>> ___
>> 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
>>
> ___
> 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
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

Sorry I was OK, I have made it a bug report to save bandwidth here.

I assume you can logon to Jenkins? It is much easier to check it out there.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 04.04.2023 um 21:04 schrieb Rick McGuire :
> 
> PO, please post the complete list of files with errors. The fix is correct, 
> the error is in the test cases. 
> 
> Rick
> 
> On Tue, Apr 4, 2023 at 2:56 PM P.O. Jonsson  > wrote:
> All went well and Jenkins is up again. Besides Marks M1 Mac all 
> platforms are online.
> 
> I looked at the current projects and it seems most builds pass but ALL test 
> fail with the build from 3.4.2023. The build before that. from 1.4.2023 seems 
> to have passed on most platforms.
> 
> On CentOS there are 59 Failures and 20 Errors, here some of them
> 
> caselessLastpos.testGroup
> lastpos.testGroup 
> caselessWordPos.testGroup
> overlay.testGroup
> String_verifyMethod.testGroup
> String_wordposMethod.testGroup
> String_bitorMethod.testGroup
> bitxor.testGroup
> caselessCompare.testGroup
> 
> But there are more. Please review the latest commit.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
>> Am 04.04.2023 um 15:48 schrieb P.O. Jonsson > >:
>> 
>> I am making a 2nd attempt to replace my cable modem/router today and 
>> tomorrow, so Jenkins may be unavailable for some time.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>> 
>> ___
>> 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 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[Rick McGuire]

PO, please post the complete list of files with errors. The fix is correct,
the error is in the test cases.

Rick

On Tue, Apr 4, 2023 at 2:56 PM P.O. Jonsson  wrote:

> All went well and Jenkins is up again. Besides Marks M1 Mac all
> platforms are online.
>
> I looked at the current projects and it seems most builds pass but ALL
> test fail with the build from 3.4.2023. The build before that. from
> 1.4.2023 seems to have passed on most platforms.
>
> On CentOS there are 59 Failures and 20 Errors, here some of them
>
> caselessLastpos.testGroup
> lastpos.testGroup
> caselessWordPos.testGroup
> overlay.testGroup
> String_verifyMethod.testGroup
> String_wordposMethod.testGroup
> String_bitorMethod.testGroup
> bitxor.testGroup
> caselessCompare.testGroup
>
> But there are more. Please review the latest commit.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
>
> Am 04.04.2023 um 15:48 schrieb P.O. Jonsson :
>
> I am making a 2nd attempt to replace my cable modem/router today and
> tomorrow, so Jenkins may be unavailable for some time.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
>
> ___
> 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
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

All went well and Jenkins is up again. Besides Marks M1 Mac all 
platforms are online.

I looked at the current projects and it seems most builds pass but ALL test 
fail with the build from 3.4.2023. The build before that. from 1.4.2023 seems 
to have passed on most platforms.

On CentOS there are 59 Failures and 20 Errors, here some of them

caselessLastpos.testGroup
lastpos.testGroup 
caselessWordPos.testGroup
overlay.testGroup
String_verifyMethod.testGroup
String_wordposMethod.testGroup
String_bitorMethod.testGroup
bitxor.testGroup
caselessCompare.testGroup

But there are more. Please review the latest commit.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 04.04.2023 um 15:48 schrieb P.O. Jonsson :
> 
> I am making a 2nd attempt to replace my cable modem/router today and 
> tomorrow, so Jenkins may be unavailable for some time.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[René Jansen]

hi P.O.,Thanks!René.On 4 Apr 2023, at 15:49, P.O. Jonsson  wrote:I am making a 2nd attempt to replace my cable modem/router today and tomorrow, so Jenkins may be unavailable for some time.
Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se


___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[rvjan...@xs4all.nl]

Rony,

If you have an account I can attach the privileges to it. You can make an 
account on the machine itself.

René.

> On 11 Feb 2023, at 19:39, P. O. Jonsson  wrote:
> 
> Ah sorry I thought you had access.
> 
> @Rene’: can you set up an account for Rony? I am on the road for a couple of 
> days.
> 
> Von meinem iPhone gesendet
> 
>> Am 11.02.2023 um 17:48 schrieb Rony G. Flatscher :
>> 
>> Hi P.O.,
>> 
 On 11.02.2023 16:51, ooRexx wrote:
>>> Short info:
>>> 
>>> The JSON.testGroup is failing on most *nixes, please have a look whoever 
>>> wrote it (Rony?)
>> 
>> Can you please make one or all of the logs available?
>> 
>> Without them it is a little bit hard to see what goes wrong... :)
>> 
>> Regards,
>> 
>> ---rony
>> 
>> 
>> ___
>> 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



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P. O. Jonsson]

Ah sorry I thought you had access.

@Rene’: can you set up an account for Rony? I am on the road for a couple of 
days.

Von meinem iPhone gesendet

> Am 11.02.2023 um 17:48 schrieb Rony G. Flatscher :
> 
> Hi P.O.,
> 
>> On 11.02.2023 16:51, ooRexx wrote:
>> Short info:
>> 
>> The JSON.testGroup is failing on most *nixes, please have a look whoever 
>> wrote it (Rony?)
> 
> Can you please make one or all of the logs available?
> 
> Without them it is a little bit hard to see what goes wrong... :)
> 
> Regards,
> 
> ---rony
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[Rony G. Flatscher]

Hi P.O.,

On 11.02.2023 16:51, ooRexx wrote:

Short info:

The JSON.testGroup is failing on most *nixes, please have a look whoever wrote 
it (Rony?)


Can you please make one or all of the logs available?

Without them it is a little bit hard to see what goes wrong... :)

Regards,

---rony


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins Heads-up

[P.O. Jonsson]

Ok, now all machines are up and running. ooDialog has been built successfully 
and uploaded to Sourceforge. As soon as a change is committee it will be 
rebuilt again. ooDialog is a tough cookie to build with almost 1900 pages so it 
can take some time before you see it, last build took 23 minutes all-in-all.

Thanks Jon for caring about this book.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 06.02.2023 um 22:59 schrieb Sahananda Sahananda :
> 
> Thanks P.O.
> 
> Jon
> 
> On Mon, 6 Feb 2023 at 21:57, ooRexx  > wrote:
> I failed to notice that the machine used for building the documentation was 
> offline for some time. I have reconnected it and it will start to rebuild any 
> changed documentation within an hour or so.
> 
> This line seems to take ages to get past, seems to be a huge file. What is it?
> 
> AoorexxdocSVN/tools/RailRoadDiagrams/rr-1.67-java8.zip
> 
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins Heads-up

[Sahananda Sahananda]

Thanks P.O.

Jon

On Mon, 6 Feb 2023 at 21:57, ooRexx  wrote:

> I failed to notice that the machine used for building the documentation
> was offline for some time. I have reconnected it and it will start to
> rebuild any changed documentation within an hour or so.
>
> This line seems to take ages to get past, seems to be a huge file. What is
> it?
>
> AoorexxdocSVN/tools/RailRoadDiagrams/rr-1.67-java8.zip
>
>
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> ___
> 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

Re: [Oorexx-devel] Jenkins

[René Jansen]

Well, the Rockhopper which ran the IBMZ Jenkins client is a Z12 running z/VM 6.4 running Ubuntu for Z. As soon as the electrical power prices normalize it will be switched on again - according to the owner - and we can have a look. As an alternative we can try QEMU and see what that does.René.On 14 Nov 2022, at 11:42, P.O. Jonsson  wrote:Am 14.11.2022 um 15:41 schrieb Dave Jones <vmda...@gmail.com>:Hello, all.Does this problem occur when the virtual machines are hosted by a *real* hypervisor, namely z/VM? :-)I which I had a S/390 running z/VM to play with. And a nuclear reactor to power it with... Or is it just something that happens on VMWare?We use Oracle VirtualBox, not VMWare but I think it is the underlying (desktop) hardware that creates the timing fuss.MAny thanks.DJOn Sun, Nov 13, 2022 at 1:39 PM Mike Cowlishaw <m...@speleotrove.com> wrote:




OK, thanks!

  
  
  From: Rick McGuire 
  [mailto:object.r...@gmail.com] Sent: 13 November 2022 
  11:13To: Open Object Rexx Developer Mailing ListSubject: 
  Re: [Oorexx-devel] Jenkins
  
  
  
  
  On Sun, Nov 13, 2022 at 5:57 AM Mike Cowlishaw 
  <m...@speleotrove.com> 
  wrote:
  

 

  
I'm not familiar with internals of ooRexx, but reading 
this:
I tried to "tune" Virtualbox to get rid of the 
  timing error problems but every attempt actually made things 
  worse, with more than half of the timing tests failing. I have 
  reset Virtualbox to default values now. What *DID* help on the 
  other hand was to deprive the VMs of resources. Changing from 
  2 cores/4 GB memory to 1 core/ 2 GB memory made all *nixes 
  pass all tests, so it looks like the problem were related to 
  Virtualbox rather than to ooRexx. Only exception are the BSDs, 
  that are still a bit problematic to test. But all platforms (Win 
  macOS Linux Unix) build without error now.makes me 
wonder a bit: by reducing to one core then anything multithreadedis 
forced to run on a single thread which makes race conditions much 
lesslikely than when on multicore where multiple threads can run 
simultaneously.
  ooRexx is not truly multithreaded. Only one thread at a time is allowed 
  to run Rexx code at a time, with a cooperative internal dispatch mechanism. 
  Only threads running external code (e.g., calls to native libraries or running 
  commands) truly run concurrently.  Multiple cores might affect the timing 
  of which thread happens to get permission to run next, but which thread gets 
  permission has always been unpredictable. 
  
   
  


  

  Which means that there can be no unexpected time glitches between 
  threads since they run consecutively on one core. And that ooRexx handles 
  any such race conditions GREAT. This shows IMO how robust ooRexx 5 has 
  become. Gold standard ;-) 
Right, but in the real 
world it will be running on multicore 
  machines...
   
  The failing test cases run just fine on multicore machines, they only 
  seem to fail in multicore virtual machines. Also, the failures don't really 
  appear to be race conditions, but rather checks in timer values that are 
  falling outside expected ranges. There's something funny going on with the 
  clocks in the virtual machines in those situations. 
  
   
  

 
Mike ___Oorexx-devel 
mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins update

[René Jansen]

Very good!René.On 13 Nov 2022, at 18:47, P.O. Jonsson  wrote:We now have a Manjaro Linux client running on Raspberry Pi 3B+ (SoC Broadcom BCM2837B0  CPU ARM Cortex-A53). Build and test worked on the first try without errors. I only have to figure out how to build a package and we have support for aarch64. 
Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se


___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

> Am 14.11.2022 um 15:41 schrieb Dave Jones :
> 
> Hello, all.
> Does this problem occur when the virtual machines are hosted by a *real* 
> hypervisor, namely z/VM? :-)

I which I had a S/390 running z/VM to play with. And a nuclear reactor to power 
it with...

> Or is it just something that happens on VMWare?

We use Oracle VirtualBox, not VMWare but I think it is the underlying (desktop) 
hardware that creates the timing fuss.

> MAny thanks.
> DJ
> 
> On Sun, Nov 13, 2022 at 1:39 PM Mike Cowlishaw  <mailto:m...@speleotrove.com>> wrote:
> OK, thanks!
> 
> From: Rick McGuire [mailto:object.r...@gmail.com 
> <mailto:object.r...@gmail.com>] 
> Sent: 13 November 2022 11:13
> To: Open Object Rexx Developer Mailing List
> Subject: Re: [Oorexx-devel] Jenkins
> 
> 
> 
> On Sun, Nov 13, 2022 at 5:57 AM Mike Cowlishaw  <mailto:m...@speleotrove.com>> wrote:
> 
>  
>> I'm not familiar with internals of ooRexx, but reading this:
>> 
>>> I tried to "tune" Virtualbox to get rid of the timing error 
>>> problems but every attempt actually made things worse, with 
>>> more than half of the timing tests failing. I have reset 
>>> Virtualbox to default values now. What *DID* help on the 
>>> other hand was to deprive the VMs of resources. Changing from 
>>> 2 cores/4 GB memory to 1 core/ 2 GB memory made all *nixes 
>>> pass all tests, so it looks like the problem were related to 
>>> Virtualbox rather than to ooRexx. Only exception are the 
>>> BSDs, that are still a bit problematic to test. But all 
>>> platforms (Win macOS Linux Unix) build without error now.
>> 
>> makes me wonder a bit: by reducing to one core then anything multithreaded
>> is forced to run on a single thread which makes race conditions much less
>> likely than when on multicore where multiple threads can run simultaneously.
> 
> ooRexx is not truly multithreaded. Only one thread at a time is allowed to 
> run Rexx code at a time, with a cooperative internal dispatch mechanism. Only 
> threads running external code (e.g., calls to native libraries or running 
> commands) truly run concurrently.  Multiple cores might affect the timing of 
> which thread happens to get permission to run next, but which thread gets 
> permission has always been unpredictable. 
> 
>  
>> 
> Which means that there can be no unexpected time glitches between threads 
> since they run consecutively on one core. And that ooRexx handles any such 
> race conditions GREAT. This shows IMO how robust ooRexx 5 has become. Gold 
> standard ;-) 
> 
> Right, but in the real world it will be running on multicore machines...
>  
> The failing test cases run just fine on multicore machines, they only seem to 
> fail in multicore virtual machines. Also, the failures don't really appear to 
> be race conditions, but rather checks in timer values that are falling 
> outside expected ranges. There's something funny going on with the clocks in 
> the virtual machines in those situations. 
> 
>  
>  
> Mike 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net <mailto:Oorexx-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net <mailto:Oorexx-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
> <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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[Dave Jones]

Hello, all.
Does this problem occur when the virtual machines are hosted by a *real*
hypervisor, namely z/VM? :-) Or is it just something that happens on VMWare?
MAny thanks.
DJ

On Sun, Nov 13, 2022 at 1:39 PM Mike Cowlishaw  wrote:

> OK, thanks!
>
> --
> *From:* Rick McGuire [mailto:object.r...@gmail.com]
> *Sent:* 13 November 2022 11:13
> *To:* Open Object Rexx Developer Mailing List
> *Subject:* Re: [Oorexx-devel] Jenkins
>
>
>
> On Sun, Nov 13, 2022 at 5:57 AM Mike Cowlishaw 
> wrote:
>
>>
>>
>>
>> I'm not familiar with internals of ooRexx, but reading this:
>>
>> I tried to "tune" Virtualbox to get rid of the timing error
>> problems but every attempt actually made things worse, with
>> more than half of the timing tests failing. I have reset
>> Virtualbox to default values now. What *DID* help on the
>> other hand was to deprive the VMs of resources. Changing from
>> 2 cores/4 GB memory to 1 core/ 2 GB memory made all *nixes
>> pass all tests, so it looks like the problem were related to
>> Virtualbox rather than to ooRexx. Only exception are the
>> BSDs, that are still a bit problematic to test. But all
>> platforms (Win macOS Linux Unix) build without error now.
>>
>>
>> makes me wonder a bit: by reducing to one core then anything multithreaded
>> is forced to run on a single thread which makes race conditions much less
>> likely than when on multicore where multiple threads can run
>> simultaneously.
>>
>> ooRexx is not truly multithreaded. Only one thread at a time is allowed
> to run Rexx code at a time, with a cooperative internal dispatch mechanism.
> Only threads running external code (e.g., calls to native libraries or
> running commands) truly run concurrently.  Multiple cores might affect the
> timing of which thread happens to get permission to run next, but which
> thread gets permission has always been unpredictable.
>
>
>
>>
>> Which means that there can be no unexpected time glitches between threads
>> since they run consecutively on one core. And that ooRexx handles any such
>> race conditions GREAT. This shows IMO how robust ooRexx 5 has become. Gold
>> standard ;-)
>>
>> Right, but in the real world it will be running on multicore machines...
>>
>
> The failing test cases run just fine on multicore machines, they only seem
> to fail in multicore virtual machines. Also, the failures don't really
> appear to be race conditions, but rather checks in timer values that are
> falling outside expected ranges. There's something funny going on with the
> clocks in the virtual machines in those situations.
>
>
>
>>
>> Mike
>> ___
>> 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
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins update

[Rony]

Wow, great work, kudos!—-ronyRony G. Flatscher (mobil/e)Am 13.11.2022 um 23:47 schrieb P.O. Jonsson :We now have a Manjaro Linux client running on Raspberry Pi 3B+ (SoC Broadcom BCM2837B0  CPU ARM Cortex-A53). Build and test worked on the first try without errors. I only have to figure out how to build a package and we have support for aarch64. 
Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se


___Oorexx-devel mailing listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[Mike Cowlishaw]

OK, thanks!


  _  

From: Rick McGuire [mailto:object.r...@gmail.com] 
Sent: 13 November 2022 11:13
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] Jenkins




On Sun, Nov 13, 2022 at 5:57 AM Mike Cowlishaw  wrote:




 

I'm not familiar with internals of ooRexx, but reading this:



I tried to "tune" Virtualbox to get rid of the timing error 
problems but every attempt actually made things worse, with 
more than half of the timing tests failing. I have reset 
Virtualbox to default values now. What *DID* help on the 
other hand was to deprive the VMs of resources. Changing from 
2 cores/4 GB memory to 1 core/ 2 GB memory made all *nixes 
pass all tests, so it looks like the problem were related to 
Virtualbox rather than to ooRexx. Only exception are the 
BSDs, that are still a bit problematic to test. But all 
platforms (Win macOS Linux Unix) build without error now.



makes me wonder a bit: by reducing to one core then anything multithreaded
is forced to run on a single thread which makes race conditions much less
likely than when on multicore where multiple threads can run simultaneously.


ooRexx is not truly multithreaded. Only one thread at a time is allowed to
run Rexx code at a time, with a cooperative internal dispatch mechanism.
Only threads running external code (e.g., calls to native libraries or
running commands) truly run concurrently.  Multiple cores might affect the
timing of which thread happens to get permission to run next, but which
thread gets permission has always been unpredictable. 

 


Which means that there can be no unexpected time glitches between threads
since they run consecutively on one core. And that ooRexx handles any such
race conditions GREAT. This shows IMO how robust ooRexx 5 has become. Gold
standard ;-) 



Right, but in the real world it will be running on multicore machines...

 
The failing test cases run just fine on multicore machines, they only seem
to fail in multicore virtual machines. Also, the failures don't really
appear to be race conditions, but rather checks in timer values that are
falling outside expected ranges. There's something funny going on with the
clocks in the virtual machines in those situations. 

 

 
Mike 
___
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

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

> Am 13.11.2022 um 12:12 schrieb Rick McGuire :
> 
>  There's something funny going on with the clocks in the virtual machines in 
> those situations. 

Maybe we should check with Einstein on time invariance in different reference 
frames… but indeed this is most likely a problem with Virtualbox, not ooRexx. 
Which is quite comforting, these timing problems have been nagging me for a 
long time.

/P.O.


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[Michael Lueck]

Greetings ooRexx'ers,


Rick McGuire wrote:



On Sun, Nov 13, 2022 at 5:57 AM Mike Cowlishaw mailto:m...@speleotrove.com>> wrote:


makes me wonder a bit: by reducing to one core then anything 
multithreaded
is forced to run on a single thread which makes race conditions much 
less
likely than when on multicore where multiple threads can run 
simultaneously.


ooRexx is not truly multithreaded. Only one thread at a time is allowed to run Rexx code at a time, with a cooperative internal dispatch mechanism. Only threads running external code (e.g., calls to 
native libraries or running commands) truly run concurrently.  Multiple cores might affect the timing of which thread happens to get permission to run next, but which thread gets permission has always 
been unpredictable.



Interesting to learn, Rick. I never realized this about ORexx/ooRexx.

So a better design would be to start many ooRexx PIDs and have each one be 
single threaded, let the OS manage the PIDs/threads, to achieve Rexx parallel 
processing, correct?

I am thankful,

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


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[Rick McGuire]

On Sun, Nov 13, 2022 at 5:57 AM Mike Cowlishaw  wrote:

>
>
>
> I'm not familiar with internals of ooRexx, but reading this:
>
> I tried to "tune" Virtualbox to get rid of the timing error
> problems but every attempt actually made things worse, with
> more than half of the timing tests failing. I have reset
> Virtualbox to default values now. What *DID* help on the
> other hand was to deprive the VMs of resources. Changing from
> 2 cores/4 GB memory to 1 core/ 2 GB memory made all *nixes
> pass all tests, so it looks like the problem were related to
> Virtualbox rather than to ooRexx. Only exception are the
> BSDs, that are still a bit problematic to test. But all
> platforms (Win macOS Linux Unix) build without error now.
>
>
> makes me wonder a bit: by reducing to one core then anything multithreaded
> is forced to run on a single thread which makes race conditions much less
> likely than when on multicore where multiple threads can run
> simultaneously.
>
> ooRexx is not truly multithreaded. Only one thread at a time is allowed to
run Rexx code at a time, with a cooperative internal dispatch mechanism.
Only threads running external code (e.g., calls to native libraries or
running commands) truly run concurrently.  Multiple cores might affect the
timing of which thread happens to get permission to run next, but which
thread gets permission has always been unpredictable.



>
> Which means that there can be no unexpected time glitches between threads
> since they run consecutively on one core. And that ooRexx handles any such
> race conditions GREAT. This shows IMO how robust ooRexx 5 has become. Gold
> standard ;-)
>
> Right, but in the real world it will be running on multicore machines...
>

The failing test cases run just fine on multicore machines, they only seem
to fail in multicore virtual machines. Also, the failures don't really
appear to be race conditions, but rather checks in timer values that are
falling outside expected ranges. There's something funny going on with the
clocks in the virtual machines in those situations.



>
> Mike
> ___
> 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

Re: [Oorexx-devel] Jenkins

[Mike Cowlishaw]

 

I'm not familiar with internals of ooRexx, but reading this:



I tried to "tune" Virtualbox to get rid of the timing error 
problems but every attempt actually made things worse, with 
more than half of the timing tests failing. I have reset 
Virtualbox to default values now. What *DID* help on the 
other hand was to deprive the VMs of resources. Changing from 
2 cores/4 GB memory to 1 core/ 2 GB memory made all *nixes 
pass all tests, so it looks like the problem were related to 
Virtualbox rather than to ooRexx. Only exception are the 
BSDs, that are still a bit problematic to test. But all 
platforms (Win macOS Linux Unix) build without error now.



makes me wonder a bit: by reducing to one core then anything multithreaded
is forced to run on a single thread which makes race conditions much less
likely than when on multicore where multiple threads can run simultaneously.



Which means that there can be no unexpected time glitches between threads
since they run consecutively on one core. And that ooRexx handles any such
race conditions GREAT. This shows IMO how robust ooRexx 5 has become. Gold
standard ;-) 



Right, but in the real world it will be running on multicore machines...
 
Mike 
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

> Am 12.11.2022 um 20:45 schrieb Mike Cowlishaw :
> 
> Good work! 
> 
Thanks!

> I'm not familiar with internals of ooRexx, but reading this:
> 
>> I tried to "tune" Virtualbox to get rid of the timing error 
>> problems but every attempt actually made things worse, with 
>> more than half of the timing tests failing. I have reset 
>> Virtualbox to default values now. What *DID* help on the 
>> other hand was to deprive the VMs of resources. Changing from 
>> 2 cores/4 GB memory to 1 core/ 2 GB memory made all *nixes 
>> pass all tests, so it looks like the problem were related to 
>> Virtualbox rather than to ooRexx. Only exception are the 
>> BSDs, that are still a bit problematic to test. But all 
>> platforms (Win macOS Linux Unix) build without error now.
> 
> makes me wonder a bit: by reducing to one core then anything multithreaded
> is forced to run on a single thread which makes race conditions much less
> likely than when on multicore where multiple threads can run simultaneously.
> 
> Mike
> 
> 
Which means that there can be no unexpected time glitches between threads since 
they run consecutively on one core. And that ooRexx handles any such race 
conditions GREAT. This shows IMO how robust ooRexx 5 has become. Gold standard 
;-)

VirtualBox is running on conventional desktop hardware without any dedicated 
hardware for the hypervisor (unlike in IBM HW). I think this is one reason we 
cannot expect multitasking in a VirtualBox VM to run completely reliable. The 
host, be it macOS or Windows (I have Virtualbox running on both), is not a 
realtime OS, like DEC RT11. That is the other reason I think. It was never 
designed to run VMs on.

I am adding Manjaro Linux to the Zoo now, running on a Raspberry Pi 3B+, this 
will make it possible to test ooRexx on aarch64 hardware.

/P.O.

> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[Mike Cowlishaw]

Good work! 

I'm not familiar with internals of ooRexx, but reading this:

> I tried to "tune" Virtualbox to get rid of the timing error 
> problems but every attempt actually made things worse, with 
> more than half of the timing tests failing. I have reset 
> Virtualbox to default values now. What *DID* help on the 
> other hand was to deprive the VMs of resources. Changing from 
> 2 cores/4 GB memory to 1 core/ 2 GB memory made all *nixes 
> pass all tests, so it looks like the problem were related to 
> Virtualbox rather than to ooRexx. Only exception are the 
> BSDs, that are still a bit problematic to test. But all 
> platforms (Win macOS Linux Unix) build without error now.

makes me wonder a bit: by reducing to one core then anything multithreaded
is forced to run on a single thread which makes race conditions much less
likely than when on multicore where multiple threads can run simultaneously.

Mike



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

> Am 22.04.2022 um 06:48 schrieb Erich Steinböck :
> 
> Hi P.O.,
> docs say "If you’re upgrading your Jenkins controller to run on Java 11, you 
> also need to upgrade the JVM on your agents".
> I don't know if Java 11 is available for all our current agents, like on the 
> zLinux.

Ok, I have silenced the warning, let´s see in September what we will have to 
do. Running Jenkins with unsupported JAVA may quickly become unbearable. Time 
will tell.
/P.O.

>  ___
> 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

Re: [Oorexx-devel] Jenkins

[Erich Steinböck]

Hi P.O.,
docs say "If you’re upgrading your Jenkins controller to run on Java 11,
you also need to upgrade the JVM on your agents".
I don't know if Java 11 is available for all our current agents, like on
the zLinux.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[René Jansen]

Hi P.O.,

For NetRexx, which is also built on this machine, there is no impediment to 
move to Java 11 or higher.

Best regards,

René.


> On 21 Apr 2022, at 23:05, P.O. Jonsson  wrote:
> 
> I have just updated Jenkins Controller to the latest version and upgraded all 
> plugins and all went well. There is however a warning:
> 
> "You are running Jenkins on Java 1.8, support for which will end on or after 
> September 1, 2022. Please refer to the documentation 
>  for 
> details on upgrading to Java 11."
> 
> I have used Java 1.8 in most places of Jenkins in the past, including all the 
> agents and in the Controller, and I seem to remember there was an issue with 
> Java 11 for the nginx server used for https support so I am hesitant to do 
> this change, but I guess it is inevitable at some point. Any objections if I 
> give it a try? Is there a reason why we should not go to JAVA 11?
> 
> If you have planned work to commit let me know and I will postpone it, there 
> is still plenty of time.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins build server

[P.O. Jonsson]

Ok, so it is possible to reach Jenkins again, and building works for all 
platforms except the M1 macOS platform that is offline.

Currently you can not use any of ssh, vnc or rdp to reach a specific machine, 
this will take some time to get back.

P.O. Jonsson
oor...@jonases.se



> Am 19.03.2022 um 21:53 schrieb P.O. Jonsson :
> 
> Dear all,
> 
> Please be aware that Jenkins may be unavailable for some time. For the 2nd 
> time in a short while all my forwarding rules in the router were lost. 
> Googling the issue hints at a problem with corrupt NVRAM in the Router, so I 
> might need to upgrade. 
> 
> Jenkins itself is purring along just fine, only you cannot reach it right 
> now. Sorry about that.
> 
> P.O. Jonsson
> oor...@jonases.se
> 
> 
> 
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins build machine

[P. O. Jonsson]

2.319 was offered by Jenkins. Now when we are up to speed we might just go for 
2.320

I did the update by replacing the “jar” file this is NOT recommended it wipes 
all plugins

There must be a better way but I did not look for it, if you have the time 
please go ahead and update it

Von meinem iPhone gesendet

> Am 25.01.2022 um 18:19 schrieb Erich Steinböck :
> 
> 
> Hi P.O.,
> I've just updated all plug-ins - so we should be clean now.
> 
> The only plug-in which has a newer version is "Pipeline: Job", but this newer 
> version needs Jenkins 2.320, while we're on 2.319.
> Why did we go for 2.319?
> Jenkins now doesn't seem to show an update notice for Jenkins itself (to 
> 2.320 or newer)
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins build machine

[Erich Steinböck]

Hi P.O.,
I've just updated all plug-ins - so we should be clean now.

The only plug-in which has a newer version is "Pipeline: Job", but this
newer version needs Jenkins 2.320, while we're on 2.319.
Why did we go for 2.319?
Jenkins now doesn't seem to show an update notice for Jenkins itself (to
2.320 or newer)
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P. O. Jonsson]

I will give it another shot in a couple of weeks I go off grid for some time 
now.

Von meinem iPhone gesendet

> Am 20.09.2021 um 12:57 schrieb René Jansen :
> 
> Hi P.O.,
> 
> I did that some two years ago in a previous job with Windows 10, WSL and a 
> Ubuntu installed from the Microsoft store. But I remember there was something 
> funny with the Windows machine that made that scenario fail every 5 days or 
> so (I suspected clock skew at the time, but I was happy to dump that machine).
> 
> The bios setting for ‘restart after power failure’ should work, though.
> 
> Best regards,
> 
> René.
> 
> 
>> On 20 Sep 2021, at 10:46, P.O. Jonsson  wrote:
>> 
>> Hi Erich and thanks, I have done just that and even set up an Agent to start 
>> all the VMs. Unfortunately it does not work and also this machine does not 
>> come back up again after power off (which it should) so I will leave it on 
>> for the time being, I have updated Virtualbox and installed all updates on 
>> all the VMs, some 100s of updates. There is some problem with CentOS, will 
>> fix that in the coming days.
>> 
>> If you have any idea on how to make passwordless ssh from a Mac to a Windows 
>> machine I would be glad to hear about it. Mac to Linux/Unix is no problem 
>> but I cannot make the Windows ssh server respond correctly, not on Windows 
>> 7, 8.1 or 10.
>> 
>> PS Do we have a Windows 11 available for testing yet?
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>> 
>> 
>> 
>>> Am 19.09.2021 um 10:47 schrieb Erich Steinböck :
>>> 
>>> Hi P.O,
 If this is an option I can put this machine on a separate switch and make 
 it available with short term (1/2 day) notice.
 As it is now it is idle 99% of the time and it is a waste of energy to 
 have it up all the time.
>>> I totally understand and agree.
>>> 
>>> If easier to implement you might make the VMs available for e.g. just one 
>>> hour per day on midnight.
>>> Any Jenkins jobs would wait until the VM becomes available at the given 
>>> time.
>>> 
>>> ___
>>> 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
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[René Jansen]

Hi P.O.,

I did that some two years ago in a previous job with Windows 10, WSL and a 
Ubuntu installed from the Microsoft store. But I remember there was something 
funny with the Windows machine that made that scenario fail every 5 days or so 
(I suspected clock skew at the time, but I was happy to dump that machine).

The bios setting for ‘restart after power failure’ should work, though.

Best regards,

René.


> On 20 Sep 2021, at 10:46, P.O. Jonsson  wrote:
> 
> Hi Erich and thanks, I have done just that and even set up an Agent to start 
> all the VMs. Unfortunately it does not work and also this machine does not 
> come back up again after power off (which it should) so I will leave it on 
> for the time being, I have updated Virtualbox and installed all updates on 
> all the VMs, some 100s of updates. There is some problem with CentOS, will 
> fix that in the coming days.
> 
> If you have any idea on how to make passwordless ssh from a Mac to a Windows 
> machine I would be glad to hear about it. Mac to Linux/Unix is no problem but 
> I cannot make the Windows ssh server respond correctly, not on Windows 7, 8.1 
> or 10.
> 
> PS Do we have a Windows 11 available for testing yet?
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
>> Am 19.09.2021 um 10:47 schrieb Erich Steinböck > >:
>> 
>> Hi P.O,
>> If this is an option I can put this machine on a separate switch and make it 
>> available with short term (1/2 day) notice.
>> As it is now it is idle 99% of the time and it is a waste of energy to have 
>> it up all the time.
>> I totally understand and agree.
>> 
>> If easier to implement you might make the VMs available for e.g. just one 
>> hour per day on midnight.
>> Any Jenkins jobs would wait until the VM becomes available at the given time.
>> 
>> ___
>> 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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

Hi Erich and thanks, I have done just that and even set up an Agent to start 
all the VMs. Unfortunately it does not work and also this machine does not come 
back up again after power off (which it should) so I will leave it on for the 
time being, I have updated Virtualbox and installed all updates on all the VMs, 
some 100s of updates. There is some problem with CentOS, will fix that in the 
coming days.

If you have any idea on how to make passwordless ssh from a Mac to a Windows 
machine I would be glad to hear about it. Mac to Linux/Unix is no problem but I 
cannot make the Windows ssh server respond correctly, not on Windows 7, 8.1 or 
10.

PS Do we have a Windows 11 available for testing yet?

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 19.09.2021 um 10:47 schrieb Erich Steinböck :
> 
> Hi P.O,
> If this is an option I can put this machine on a separate switch and make it 
> available with short term (1/2 day) notice.
> As it is now it is idle 99% of the time and it is a waste of energy to have 
> it up all the time.
> I totally understand and agree.
> 
> If easier to implement you might make the VMs available for e.g. just one 
> hour per day on midnight.
> Any Jenkins jobs would wait until the VM becomes available at the given time.
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins

[Erich Steinböck]

Hi P.O,

> If this is an option I can put this machine on a separate switch and make
> it available with short term (1/2 day) notice.
> As it is now it is idle 99% of the time and it is a waste of energy to
> have it up all the time.
>
I totally understand and agree.

If easier to implement you might make the VMs available for e.g. just one
hour per day on midnight.
Any Jenkins jobs would wait until the VM becomes available at the given
time.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

Hi,

I already have a switch for the rest of the system that I can control from 
remote but not on this machine that I set up just to have something to work 
with. Using the cloud might turn out to be expensive since we will have to pay 
for at least one core for each virtual machine, I have eleven (+4 inactive 
Android) cores reserved (out of 24). Also we will have to purchase Windows 7 
and 8 licenses again since the ones I have purchased are not relocatable. 
Hibernate does not play well with remote connections.

If this is an option I can put this machine on a separate switch and make it 
available with short term (1/2 day) notice. As it is now it is idle 99% of the 
time and it is a waste of energy to have it up all the time.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 17.09.2021 um 17:01 schrieb René Jansen :
> 
> Well yes you asked the developers … they should check Jenkins to see if they 
> broke other platforms. If you ask me, then I would suggest some more energy 
> efficient platform, or maybe a raspberry that checks if there were updates 
> and then trigger a relay that restores current to the build machine. If you 
> then tell the bios of that machine to resume after power loss, you can just 
> set the hibernate on that machine to kick in when it’s idle. Instead of a 
> relay (which I like because it leaves no doubt if the machine is off, I used 
> IKEA’s stuff), you can combine hibernate and wake-on-lan. But course it is 
> your machine, your home and your choice.
> 
> If push comes to shove we might use RexxLA’s cloud instance for build 
> machine, or have a separate instance for that purpose.
> 
> Best regards,
> 
> René.
> 
>> On 17 Sep 2021, at 16:49, P.O. Jonsson  wrote:
>> 
>> I had expected some explicit approval/disaproval on my request :-( Given 
>> the silence I will shut down the virtual machines tonight until further 
>> activity makes it necessary to start them again.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>>> Am 16.09.2021 um 21:20 schrieb P.O. Jonsson >> >:
>>> 
>>> The Jenkins system is running fine for most of the time now but in view of 
>>> the low number of commits currently I have a request: I would like to turn 
>>> of the machine hosting all virtual machines (currently 11), and turn it on 
>>> only when there is major activity. The reason being that the machine is 
>>> heating my study with +5 degrees even when its s in standby (200-250 watt 
>>> permanently). Would that be acceptable to the developers?
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>> 
>>> 
>>> 
>>> ___
>>> 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
> ___
> 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

Re: [Oorexx-devel] Jenkins

[René Jansen]

Well yes you asked the developers … they should check Jenkins to see if they 
broke other platforms. If you ask me, then I would suggest some more energy 
efficient platform, or maybe a raspberry that checks if there were updates and 
then trigger a relay that restores current to the build machine. If you then 
tell the bios of that machine to resume after power loss, you can just set the 
hibernate on that machine to kick in when it’s idle. Instead of a relay (which 
I like because it leaves no doubt if the machine is off, I used IKEA’s stuff), 
you can combine hibernate and wake-on-lan. But course it is your machine, your 
home and your choice.

If push comes to shove we might use RexxLA’s cloud instance for build machine, 
or have a separate instance for that purpose.

Best regards,

René.

> On 17 Sep 2021, at 16:49, P.O. Jonsson  wrote:
> 
> I had expected some explicit approval/disaproval on my request :-( Given the 
> silence I will shut down the virtual machines tonight until further activity 
> makes it necessary to start them again.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
> 
> 
> 
>> Am 16.09.2021 um 21:20 schrieb P.O. Jonsson :
>> 
>> The Jenkins system is running fine for most of the time now but in view of 
>> the low number of commits currently I have a request: I would like to turn 
>> of the machine hosting all virtual machines (currently 11), and turn it on 
>> only when there is major activity. The reason being that the machine is 
>> heating my study with +5 degrees even when its s in standby (200-250 watt 
>> permanently). Would that be acceptable to the developers?
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>> 
>> 
>> 
>> ___
>> 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
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P.O. Jonsson]

I had expected some explicit approval/disaproval on my request :-( Given the 
silence I will shut down the virtual machines tonight until further activity 
makes it necessary to start them again.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 16.09.2021 um 21:20 schrieb P.O. Jonsson :
> 
> The Jenkins system is running fine for most of the time now but in view of 
> the low number of commits currently I have a request: I would like to turn of 
> the machine hosting all virtual machines (currently 11), and turn it on only 
> when there is major activity. The reason being that the machine is heating my 
> study with +5 degrees even when its s in standby (200-250 watt permanently). 
> Would that be acceptable to the developers?
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[Erich Steinböck]

Hi René, success .. this works now.
Thanks!!!
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[René Jansen]

This is in place now, with the line that specifies the dpkg executable only.


> On 14 Jun 2021, at 17:49, Erich Steinböck  wrote:
> 
> I don't know if this works with options specified together with the allowed 
> command
> Are you sure you did sudo visudo -f /etc/sudoers.d/rvjansen as there seems to 
> be no  /etc/sudoers.d/rvjansen file
> 
> ls -l /etc/sudoers.d
> -rw-r--r-- 1 root root  31 Sep  5  2020 devops
> -r--r- 1 root root 958 Jan 18  2018 README
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[Erich Steinböck]

I don't know if this works with options specified together with the allowed
command
Are you sure you did sudo visudo -f /etc/sudoers.d/rvjansen as there seems
to be no  /etc/sudoers.d/rvjansen file

ls -l /etc/sudoers.d

-rw-r--r-- 1 root root  31 Sep  5  2020 devops
-r--r- 1 root root 958 Jan 18  2018 README
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[rvjan...@xs4all.nl]

At the moment it is:

rvjansen ALL = (root) NOPASSWD: /usr/bin/dpkg --install, /usr/bin/dpkg --remove

Both work from the command line. ‘No tty present’ is a Java thing I think.

René.

> On 14 Jun 2021, at 15:48, Erich Steinböck  wrote:
> 
> 
> Nope, sudo doesn't work - neither for dpkg --install nor for --remove
> It fails with "sudo: no tty present and no askpass program specified"
> 
> When you try it from the command line, does it work for you?
> Is it now set to " rvjansen ALL = (root) NOPASSWD: /usr/bin/dpkg" ?
> ___
> 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

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[Erich Steinböck]

Nope, sudo doesn't work - neither for dpkg --install nor for --remove
It fails with "sudo: no tty present and no askpass program specified"

When you try it from the command line, does it work for you?
Is it now set to " rvjansen ALL = (root) NOPASSWD: /usr/bin/dpkg" ?
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[rvjan...@xs4all.nl]

Hi Erich,

No, it was just /usr/bin/dpkg
Now I have specified them both, not sure if that helps.

René.

> On 14 Jun 2021, at 14:58, Erich Steinböck  wrote:
> 
> 
> Hi René,
> now sudo seems to work for dpkg --remove, but doesn't for dpkg --install
> Did you explicitly restrict sudo to dpkg --remove ?
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[Erich Steinböck]

Hi René,
now sudo seems to work for dpkg --remove, but doesn't for dpkg --install
Did you explicitly restrict sudo to dpkg --remove ?
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[rvjan...@xs4all.nl]

I did not have the (root) part. So it must be better now.
Tried the dpkg —remove oorexx
This did not complain, also because I never installed ooRexx yet, and it told 
me that.

René.

> On 14 Jun 2021, at 14:00, rvjan...@xs4all.nl wrote:
> 
> Yep, that is what I did. Let me doublecheck.
> 
> René.
> 
>> On 14 Jun 2021, at 10:11, René Jansen  wrote:
>> 
>> Hi Erich,
>> 
>> just did - let’s see if that works.
>> 
>> best regards,
>> 
>> René
>> 
 On 13 Jun 2021, at 05:06, Erich Steinböck  
 wrote:
>>> 
>>> Hi René, thanks!
>>> 
>>> Our build jobs now also test installation of the built binary package.
>>> On Ubuntu this means running dpkg --install and dpkg --remove
>>> But these require sudo to work.  Would you mind giving the rvjansen user 
>>> sudo dpkg without password?
>>> 
>>> Thanks and regards, Erich
>>> ___
>>> 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

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[rvjan...@xs4all.nl]

Yep, that is what I did. Let me doublecheck.

René.

> On 14 Jun 2021, at 10:11, René Jansen  wrote:
> 
> Hi Erich,
> 
> just did - let’s see if that works.
> 
> best regards,
> 
> René
> 
>> On 13 Jun 2021, at 05:06, Erich Steinböck  wrote:
>> 
>> Hi René, thanks!
>> 
>> Our build jobs now also test installation of the built binary package.
>> On Ubuntu this means running dpkg --install and dpkg --remove
>> But these require sudo to work.  Would you mind giving the rvjansen user 
>> sudo dpkg without password?
>> 
>> Thanks and regards, Erich
>> ___
>> 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

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[Erich Steinböck]

>
> sudo dpkg --remove oorexx
> sudo: no tty present and no askpass program specified
>
> Hi René, it doesn't work yet.

Did you do:
sudo visudo -f /etc/sudoers.d/rvjansen
rvjansen ALL = (root) NOPASSWD: /usr/bin/dpkg
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[René Jansen]

Hi Erich,

just did - let’s see if that works.

best regards,

René

> On 13 Jun 2021, at 05:06, Erich Steinböck  wrote:
> 
> Hi René, thanks!
> 
> Our build jobs now also test installation of the built binary package.
> On Ubuntu this means running dpkg --install and dpkg --remove
> But these require sudo to work.  Would you mind giving the rvjansen user sudo 
> dpkg without password?
> 
> Thanks and regards, Erich
> ___
> 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

Re: [Oorexx-devel] Jenkins: Rockhopper upgraded to CMake 3.20.3 and added local Subversion version

[Erich Steinböck]

Hi René, thanks!

Our build jobs now also test installation of the built binary package.
On Ubuntu this means running dpkg --install and dpkg --remove
But these require sudo to work.  Would you mind giving the rvjansen user
sudo dpkg without password?

Thanks and regards, Erich
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[rvjan...@xs4all.nl]

Yes, that is true. I run that build on a Raspi 4 with Ubuntu 20.04, 64 bit. You 
don’t habe to do anything for that, P.O.

René.

> On 11 Aug 2020, at 15:59, CVBruce  wrote:
> 
> I believe that RPi2 is 32bit.  You will need either an RPi3 or RPi4 for 64 
> bit.  You will also need to download a beta version of Raspberry Pi OS that 
> is 64 bit.
> 
> Until the recently released RPi4 8GB, all versions of Raspberry Pi OS were 32 
> bit.  This simplified their software distribution, needing only one .deb file 
> for all arm platforms.
> 
> RPi3 & RPi4 do have a 64 kernel, I believe, but the default tool chain is 
> 32bit, and will produce armhf binaries as opposed to aarch64.
> 
>> On Aug 11, 2020, at 6:37 AM, P. O. Jonsson  wrote:
>> 
>> I have a Raspberry Pi 2, I think that is ARM 64?
>> 
>> I can give it a try when I am back from holidays. The Pi 2 will not be 
>> permanently hooked up but for a test it is fine. 
>> 
>> Von meinem iPhone gesendet
>> 
 Am 10.08.2020 um 11:44 schrieb "rvjan...@xs4all.nl" :
 
>>> Hi P.O.,
>>> 
>>> Yes, those are mine. Was working with Mark to get regina SF builds, got 
>>> stuck. The other is an arm64 build which we did not have yet I think; this 
>>> works but fails on install; I have to sudo that.
>>> 
>>> René.
>>> 
> On 10 Aug 2020, at 11:07, P.O. Jonsson  wrote:
> 
 Dear All,
 
 I have reinstated my macOS och Raspberry Pi Jenkins slaves. I had changed 
 some ports internally and forgot to correct it in Jenkins master. All 
 builds pass right now (On all platforms except Windows the 
 EventSemaphore.testGroup is excluded awaiting a fix of bugg #1697).
 
 The following tw Projects appear to be work-in-progress, any info on the 
 status anyone?
 
 ooRexx-linux-aarch64-build/ build ooRexx on Ubuntu 18.04 on aarch64 (ARM64)
 regina-rexx Ubuntu64 build/ regina-rexx sourceforge build
 
 
 
 Hälsningar/Regards/Grüsse,
 P.O. Jonsson
 oor...@jonases.se
 
 
 
 
 ___
 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
>> ___
>> 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
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[CVBruce]

I believe that RPi2 is 32bit.  You will need either an RPi3 or RPi4 for 64 bit. 
 You will also need to download a beta version of Raspberry Pi OS that is 64 
bit.

Until the recently released RPi4 8GB, all versions of Raspberry Pi OS were 32 
bit.  This simplified their software distribution, needing only one .deb file 
for all arm platforms.

RPi3 & RPi4 do have a 64 kernel, I believe, but the default tool chain is 
32bit, and will produce armhf binaries as opposed to aarch64.

> On Aug 11, 2020, at 6:37 AM, P. O. Jonsson  wrote:
> 
> I have a Raspberry Pi 2, I think that is ARM 64?
> 
> I can give it a try when I am back from holidays. The Pi 2 will not be 
> permanently hooked up but for a test it is fine.
> 
> Von meinem iPhone gesendet
> 
>> Am 10.08.2020 um 11:44 schrieb "rvjan...@xs4all.nl" :
>> 
>> Hi P.O.,
>> 
>> Yes, those are mine. Was working with Mark to get regina SF builds, got 
>> stuck. The other is an arm64 build which we did not have yet I think; this 
>> works but fails on install; I have to sudo that.
>> 
>> René.
>> 
>>> On 10 Aug 2020, at 11:07, P.O. Jonsson  wrote:
>>> 
>>> Dear All,
>>> 
>>> I have reinstated my macOS och Raspberry Pi Jenkins slaves. I had changed 
>>> some ports internally and forgot to correct it in Jenkins master. All 
>>> builds pass right now (On all platforms except Windows the 
>>> EventSemaphore.testGroup is excluded awaiting a fix of bugg #1697).
>>> 
>>> The following tw Projects appear to be work-in-progress, any info on the 
>>> status anyone?
>>> 
>>> ooRexx-linux-aarch64-build/ build ooRexx on Ubuntu 18.04 on aarch64 (ARM64)
>>> regina-rexx Ubuntu64 build/ regina-rexx sourceforge build
>>> 
>>> 
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> 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
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel



signature.asc
Description: Message signed with OpenPGP
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[P. O. Jonsson]

I have a Raspberry Pi 2, I think that is ARM 64?

I can give it a try when I am back from holidays. The Pi 2 will not be 
permanently hooked up but for a test it is fine. 

Von meinem iPhone gesendet

> Am 10.08.2020 um 11:44 schrieb "rvjan...@xs4all.nl" :
> 
> Hi P.O.,
> 
> Yes, those are mine. Was working with Mark to get regina SF builds, got 
> stuck. The other is an arm64 build which we did not have yet I think; this 
> works but fails on install; I have to sudo that.
> 
> René.
> 
>>> On 10 Aug 2020, at 11:07, P.O. Jonsson  wrote:
>>> 
>> Dear All,
>> 
>> I have reinstated my macOS och Raspberry Pi Jenkins slaves. I had changed 
>> some ports internally and forgot to correct it in Jenkins master. All builds 
>> pass right now (On all platforms except Windows the EventSemaphore.testGroup 
>> is excluded awaiting a fix of bugg #1697).
>> 
>> The following tw Projects appear to be work-in-progress, any info on the 
>> status anyone?
>> 
>> ooRexx-linux-aarch64-build/ build ooRexx on Ubuntu 18.04 on aarch64 (ARM64)
>> regina-rexx Ubuntu64 build/ regina-rexx sourceforge build
>> 
>> 
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>> 
>> 
>> 
>> 
>> ___
>> 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
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Jenkins

[rvjan...@xs4all.nl]

Hi P.O.,

Yes, those are mine. Was working with Mark to get regina SF builds, got stuck. 
The other is an arm64 build which we did not have yet I think; this works but 
fails on install; I have to sudo that.

René.

> On 10 Aug 2020, at 11:07, P.O. Jonsson  wrote:
> 
> Dear All,
> 
> I have reinstated my macOS och Raspberry Pi Jenkins slaves. I had changed 
> some ports internally and forgot to correct it in Jenkins master. All builds 
> pass right now (On all platforms except Windows the EventSemaphore.testGroup 
> is excluded awaiting a fix of bugg #1697).
> 
> The following tw Projects appear to be work-in-progress, any info on the 
> status anyone?
> 
> ooRexx-linux-aarch64-build/ build ooRexx on Ubuntu 18.04 on aarch64 (ARM64)
> regina-rexx Ubuntu64 build/ regina-rexx sourceforge build
> 
> 
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
> 
> 
> 
> 
> ___
> 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

Re: [Oorexx-devel] Jenkins slave machines, Java Update

[P.O. Jonsson]

Dear Erich and/or René,

Now the Mac Mini is back online again. I have logged in to the Jenkins server 
and confirm that I can do a build. I could also see that the Win machine is 
also back again and have produced builds.

There was a failure for the „Test“ on the Mac mini, can you please have a look? 
Seems to have been going on for some time.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 02.09.2018 um 12:10 schrieb Erich Steinböck :
> 
> I will go ahead and update both Jenkins slaves to the latest version of Java 
> 8 then.
> 
> Hi P.O, currently our build server cannot reach your Mac Mini slave:
> [09/02/18 11:01:58] [SSH] Opening SSH connection to jonases24.asuscomm.com:22 
> .
> No route to host (Host unreachable)
> SSH Connection failed with IOException: "No route to host (Host unreachable)".
> 
> --
> 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] Jenkins slave machines, Java Update

[P.O. Jonsson]

Dear Erich,

Unfortunately the upgrade resulted in Kernel Panic, the machine does not boot 
any more :-(

I will try to recover from an earlier date, if that is not possible I will 
reinstall the machine, this will take some time I am afraid. I will let you 
know when I am ready, sorry about the interruption.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 02.09.2018 um 12:54 schrieb P.O. Jonsson :
> 
> I am working on it, after the update I shut it down by mistake, it will be up 
> in a couple of hours.
> 
> I now have all mandatory updates on both machines, Java latest version of 
> Java 8 (1.8.0.181) on the Win machine 32 and 64 bit versions, on the Mac only 
> 64 bit.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
>> Am 02.09.2018 um 12:10 schrieb Erich Steinböck > >:
>> 
>> I will go ahead and update both Jenkins slaves to the latest version of Java 
>> 8 then.
>> 
>> Hi P.O, currently our build server cannot reach your Mac Mini slave:
>> [09/02/18 11:01:58] [SSH] Opening SSH connection to 
>> jonases24.asuscomm.com:22 .
>> No route to host (Host unreachable)
>> SSH Connection failed with IOException: "No route to host (Host 
>> unreachable)".
>> 
>> --
>> 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] Jenkins slave machines, Java Update

[P.O. Jonsson]

I am working on it, after the update I shut it down by mistake, it will be up 
in a couple of hours.

I now have all mandatory updates on both machines, Java latest version of Java 
8 (1.8.0.181) on the Win machine 32 and 64 bit versions, on the Mac only 64 bit.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 02.09.2018 um 12:10 schrieb Erich Steinböck :
> 
> I will go ahead and update both Jenkins slaves to the latest version of Java 
> 8 then.
> 
> Hi P.O, currently our build server cannot reach your Mac Mini slave:
> [09/02/18 11:01:58] [SSH] Opening SSH connection to jonases24.asuscomm.com:22 
> .
> No route to host (Host unreachable)
> SSH Connection failed with IOException: "No route to host (Host unreachable)".
> 
> --
> 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] Jenkins slave machines, Java Update

[Erich Steinböck]

>
> I will go ahead and update both Jenkins slaves to the latest version of
> Java 8 then.


Hi P.O, currently our build server cannot reach your Mac Mini slave:

[09/02/18 11:01:58] [SSH] Opening SSH connection to jonases24.asuscomm.com:22.

No route to host (Host unreachable)
SSH Connection failed with IOException: "No route to host (Host unreachable)".
--
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] Jenkins slave machines, Java Update

[Erich Steinböck]

>
> are the builds on T20/Win failing?
>

Windows 10 32- and 64-bit builds and tests are running fine on your box.
Install packages are built, but the latest version isn't also installed
during build or test, so you typically wouldn't see a new version when just
running rexx -v
--
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] Jenkins slave machines, Java Update

[P.O. Jonsson]

Ok thanks for the info Rony. I will stay on Java 8 to keep the same version on 
all systems.

I will go ahead and update both Jenkins slaves to the latest version of Java 8 
then.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 01.09.2018 um 15:10 schrieb Rony :
> 
> 
> Am 01.09.2018 um 13:31 schrieb René Jansen  >:
> 
>> I don’t know about Bsf. Rony 
> Just use the latest beta of BSF4ooRexx, it‘ll work with all Java versions up 
> to the latest ones, having a baseline of Java 1.6/6. 
> 
> —-rony
> 
> Rony G. Flatscher (mobil/e)
> 
>> On 1 Sep 2018, at 12:01, P.O. Jonsson > > wrote:
>> 
>>> This is mainly for Erich and René,
>>> 
>>> I have just updated all my machines to the latest version of Java 8:
>>> 
>>> JRE Java 8 Update 181 (Standard edition 1.8.0.181-b13)
>>> JDK Java 8 Update 181
>>> 
>>> I noticed that both my Jenkins slaves (pos-mac-mini with MacOs High Sierra 
>>> and T20 With Win 10) have outdated Java versions.
>>> 
>>> Can I update them without disturbing the builds? Let me know and I will 
>>> make it and all outstanding updates today.
>>> 
>>> What about Java 10? 
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> 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 
>> 
> --
> 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] Jenkins slave machines, Java Update

[Rony]

> 
> Am 01.09.2018 um 13:31 schrieb René Jansen :
> 
> I don’t know about Bsf. Rony 
Just use the latest beta of BSF4ooRexx, it‘ll work with all Java versions up to 
the latest ones, having a baseline of Java 1.6/6. 

—-rony

Rony G. Flatscher (mobil/e)

>> On 1 Sep 2018, at 12:01, P.O. Jonsson  wrote:
>> 
>> This is mainly for Erich and René,
>> 
>> I have just updated all my machines to the latest version of Java 8:
>> 
>> JRE Java 8 Update 181 (Standard edition 1.8.0.181-b13)
>> JDK Java 8 Update 181
>> 
>> I noticed that both my Jenkins slaves (pos-mac-mini with MacOs High Sierra 
>> and T20 With Win 10) have outdated Java versions.
>> 
>> Can I update them without disturbing the builds? Let me know and I will make 
>> it and all outstanding updates today.
>> 
>> What about Java 10? 
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>> 
>> 
>> 
>> 
>> --
>> 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
--
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] Jenkins slave machines, Java Update

[René Jansen]

Hi P.O.,

Java 8 is good. Java 10 is not good for NetRexx (but I don’t build NetRexx on 
it).

I don’t know about Bsf. Rony 

Best regards,

René.

> On 1 Sep 2018, at 12:01, P.O. Jonsson  wrote:
> 
> This is mainly for Erich and René,
> 
> I have just updated all my machines to the latest version of Java 8:
> 
> JRE Java 8 Update 181 (Standard edition 1.8.0.181-b13)
> JDK Java 8 Update 181
> 
> I noticed that both my Jenkins slaves (pos-mac-mini with MacOs High Sierra 
> and T20 With Win 10) have outdated Java versions.
> 
> Can I update them without disturbing the builds? Let me know and I will make 
> it and all outstanding updates today.
> 
> What about Java 10? 
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
> 
> 
> 
> 
> --
> 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] Jenkins slave machines, Java Update

[P.O. Jonsson]

In addition:

I noted that the rexx version (rexx -v in a terminal window) on the Mac vas 
dated August 28 2018 (two days ago) but the Win version July 3 2018, are the 
builds on T20/Win failing?

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 01.09.2018 um 12:01 schrieb P.O. Jonsson :
> 
> This is mainly for Erich and René,
> 
> I have just updated all my machines to the latest version of Java 8:
> 
> JRE Java 8 Update 181 (Standard edition 1.8.0.181-b13)
> JDK Java 8 Update 181
> 
> I noticed that both my Jenkins slaves (pos-mac-mini with MacOs High Sierra 
> and T20 With Win 10) have outdated Java versions.
> 
> Can I update them without disturbing the builds? Let me know and I will make 
> it and all outstanding updates today.
> 
> What about Java 10? 
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
> --
> 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