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
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
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
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
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
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
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
>
>
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,
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
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
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
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
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
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
>
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
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
Short info:
The JSON.testGroup is failing on most *nixes, please have a look whoever wrote
it (Rony?)
The machine hosting all the VMs will be offline for a couple of days as of this
evening while being moved. Also the documentation build will be unavailable a
couple of days.
Jenkins itself
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
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
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?
A
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:
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
:
> 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 Mi
*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:
>
>>
>>
>>
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
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. Jonsson
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
> 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,
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
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
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
> 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
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.
Jenkins Master is now running Java 11 as do all the Agents. We are running a
LTS version so hopefully not so much updating work in the future.
All WM Windows are now on a dedicated host machine running Windows 10. We have
Windows 7,8.1,10 and recently 11 in VMs and they all build without
> 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
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
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
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
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
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
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
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
The Jenkins build machine has been updated, but there is a large number of
plugins that are either not working or have security issues.
I have installed a plugin „Plugin Usage“ that can be found in the left column
in the dashboard. As of tomorrow I will start removing all plugins that are
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
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
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
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
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
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
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.
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
Hi René, success .. this works now.
Thanks!!!
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
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
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
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
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" ?
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
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
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.
>
>
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
>
> 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
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
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
Dear ooRexx developers,
"to whom it may concern”:
I upgraded the Ubuntu installed CMake (which was quite old at 3.10) with a
locally built CMake 3.20.3, and removed 3.10. So for Linux on Z at least, this
is not holding Cmake features back.
Also, on Erich’s request (from some time ago, sorry
Just a short heads-up: I will be doing maintenance on the Jenkins server today
so it might be unavailable for some time. It will be up again before tonight.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
___
Oorexx-devel mailing list
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
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,
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.
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
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
Dear all,
I went in to Jenkins to check it out and saw that the Jenkins Windows slave
machine was offline again for the umptiest time :-(.
It turns out „Windows Hello“ is not initialized on the machine and this is
blocking the boot process early and therefore the automatic reconnection to
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
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
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.
>
> 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
>
> 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
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
>
> 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
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
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.
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
Dear Erich,
The Mac mini is up again after a change of disk, it should be a bit
more responsive now.
Please let me know if anything stopped working. I have cloned the old disk so
it should be identical to the previous setup but you never know.
Von meinen Macbook gesendet
Dear Erich et al,
This is just to let you know that I have turned of the MAC Jenkins slave at
jonases24.asuscomm.com for maintenance. I am putting a leftover SSD into it,
will let you know when it is up again.
Von meinen Macbook gesendet
Hälsningar/Regards/Grüsse,
P.O. Jonsson
83 matches
Mail list logo
