Smalltalk › Pharo › Pharo Smalltalk Developers

VMs build process restored

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

EstebanLM

VMs build process restored

(it was broken since december)

Which means latest vm versions are latest builds from OSVM:

64bit

• http://files.pharo.org/get-files/70/pharo64-mac-latest.zip
• http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip
• http://files.pharo.org/get-files/70/pharo64-linux-latest.zip
• http://files.pharo.org/get-files/70/pharo64-win-latest.zip
32bit

• http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip
• http://files.pharo.org/get-files/70/pharo-linux-latest.zip
• http://files.pharo.org/get-files/70/pharo-mac-latest.zip
• http://files.pharo.org/get-files/70/pharo-win-latest.zip

Hints

• MacOS VMs now are signed! This should fix a lot of problems we had before.
• Please take note that win64 build lacks all library dependencies, and many things will not work (working on that).
Thanks to Fabio to help me put all the pieces together.

cheers,
Esteban

Clément Béra

Re: VMs build process restored

Thank you very much Esteban, Thanks Fabio.

On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <[hidden email]> wrote:

(it was broken since december)

Which means latest vm versions are latest builds from OSVM:

64bit

• http://files.pharo.org/get-files/70/pharo64-mac-latest.zip
• http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip
• http://files.pharo.org/get-files/70/pharo64-linux-latest.zip
• http://files.pharo.org/get-files/70/pharo64-win-latest.zip
32bit

• http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip
• http://files.pharo.org/get-files/70/pharo-linux-latest.zip
• http://files.pharo.org/get-files/70/pharo-mac-latest.zip
• http://files.pharo.org/get-files/70/pharo-win-latest.zip

Hints

• MacOS VMs now are signed! This should fix a lot of problems we had before.
• Please take note that win64 build lacks all library dependencies, and many things will not work (working on that).
Thanks to Fabio to help me put all the pieces together.

cheers,
Esteban

Clément Béra

Pharo consortium engineer

https://clementbera.wordpress.com/

Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq

CyrilFerlicot

Re: VMs build process restored

In reply to this post by EstebanLM

Le 06/02/2018 à 17:58, Esteban Lorenzano a écrit :

> (it was broken since december)
>
> Which means latest vm versions are latest builds from OSVM:
>
> 64bit
>
> • http://files.pharo.org/get-files/70/pharo64-mac-latest.zip
> • http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip
> • http://files.pharo.org/get-files/70/pharo64-linux-latest.zip
> • http://files.pharo.org/get-files/70/pharo64-win-latest.zip
> 32bit
>
> • http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip
> • http://files.pharo.org/get-files/70/pharo-linux-latest.zip
> • http://files.pharo.org/get-files/70/pharo-mac-latest.zip
> • http://files.pharo.org/get-files/70/pharo-win-latest.zip
>
> Hints
>
> • MacOS VMs now are signed! This should fix a lot of problems we had before.
> • Please take note that win64 build lacks all library dependencies, and many things will not work (working on that).
> Thanks to Fabio to help me put all the pieces together.
>
>
> cheers,
> Esteban
>

Thank you very much!

Is it planned to release some of those vm as stable for Pharo 6.1 if
they fix the metacello loading crash in linux 64bits?

--
Cyril Ferlicot
https://ferlicot.fr

signature.asc (836 bytes) Download Attachment

Stephane Ducasse-3

Re: VMs build process restored

In reply to this post by Clément Béra

Yes thank you both!

Stef

On Tue, Feb 6, 2018 at 6:52 PM, Clément Bera <[hidden email]> wrote:

> Thank you very much Esteban, Thanks Fabio.
>
> On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <[hidden email]>
> wrote:
>>
>> (it was broken since december)
>>
>> Which means latest vm versions are latest builds from OSVM:
>>
>> 64bit
>>
>> • http://files.pharo.org/get-files/70/pharo64-mac-latest.zip
>> •
>> http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip
>> • http://files.pharo.org/get-files/70/pharo64-linux-latest.zip
>> • http://files.pharo.org/get-files/70/pharo64-win-latest.zip
>> 32bit
>>
>> •
>> http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-linux-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-mac-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-win-latest.zip
>>
>> Hints
>>
>> • MacOS VMs now are signed! This should fix a lot of problems we
>> had before.
>> • Please take note that win64 build lacks all library
>> dependencies, and many things will not work (working on that).
>> Thanks to Fabio to help me put all the pieces together.
>>
>>
>> cheers,
>> Esteban
>
>
>
>
> --
> Clément Béra
> Pharo consortium engineer
> https://clementbera.wordpress.com/
> Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq

CyrilFerlicot

Re: VMs build process restored

In reply to this post by EstebanLM

On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <[hidden email]> wrote:

) > cheers,
> Esteban

Hi!

Just a little feedback.

Currently, at Synectique, we added Pharo 61 64bits build to our
Jenkins. Those builds failed **a lot** because of segmentation faults.
We added a mechanism to retry two times when there was a segfault and
even like that we have failing builds.

Since the restoration of the vms I removed the retry mechanism and I
added a hack to use the latest Pharo 70 vm
(http://files.pharo.org/get-files/70/pharo64-linux-latest.zip) instead
of the stable pharo 61 vm. Since then, there was no crash due to the
VM.
This is a great improvement.
Then I have a question: Is it plan to release new stable 64bit vms for
Pharo 61? Currently, our builds are based on hacks and if no problem
is detected with the latest vm it would greatly help stability-wise to
have official vms that does not crash 3/5times when we load a project.
Also, I understand it can be hard to backport vms with the resources
of the community. :)

--
Cyril Ferlicot
https://ferlicot.fr

EstebanLM

Re: VMs build process restored

> On 8 Feb 2018, at 11:49, Cyril Ferlicot <[hidden email]> wrote:
>
> On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <[hidden email]> wrote:
>> (it was broken since december)
>>
>> Which means latest vm versions are latest builds from OSVM:
>>
>> 64bit
>>
>> • http://files.pharo.org/get-files/70/pharo64-mac-latest.zip
>> • http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip
>> • http://files.pharo.org/get-files/70/pharo64-linux-latest.zip
>> • http://files.pharo.org/get-files/70/pharo64-win-latest.zip
>> 32bit
>>
>> • http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-linux-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-mac-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-win-latest.zip
>>
>> Hints
>>
>> • MacOS VMs now are signed! This should fix a lot of problems we had before.
>> • Please take note that win64 build lacks all library dependencies, and many things will not work (working on that).
>> Thanks to Fabio to help me put all the pieces together.
>>
>>
> ) > cheers,
>> Esteban
>
> Hi!
>
> Just a little feedback.
>
> Currently, at Synectique, we added Pharo 61 64bits build to our
> Jenkins. Those builds failed **a lot** because of segmentation faults.
> We added a mechanism to retry two times when there was a segfault and
> even like that we have failing builds.
>
> Since the restoration of the vms I removed the retry mechanism and I
> added a hack to use the latest Pharo 70 vm
> (http://files.pharo.org/get-files/70/pharo64-linux-latest.zip) instead
> of the stable pharo 61 vm. Since then, there was no crash due to the
> VM.
> This is a great improvement.
> Then I have a question: Is it plan to release new stable 64bit vms for
> Pharo 61?

yes :)

> Currently, our builds are based on hacks and if no problem
> is detected with the latest vm it would greatly help stability-wise to
> have official vms that does not crash 3/5times when we load a project.
> Also, I understand it can be hard to backport vms with the resources
> of the community. :)
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>

Eliot Miranda-2

Re: VMs build process restored

In reply to this post by CyrilFerlicot

Hi Cyril,

> On Feb 8, 2018, at 2:49 AM, Cyril Ferlicot <[hidden email]> wrote:
>
>> On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <[hidden email]> wrote:
>> (it was broken since december)
>>
>> Which means latest vm versions are latest builds from OSVM:
>>
>> 64bit
>>
>> • http://files.pharo.org/get-files/70/pharo64-mac-latest.zip
>> • http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip
>> • http://files.pharo.org/get-files/70/pharo64-linux-latest.zip
>> • http://files.pharo.org/get-files/70/pharo64-win-latest.zip
>> 32bit
>>
>> • http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-linux-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-mac-latest.zip
>> • http://files.pharo.org/get-files/70/pharo-win-latest.zip
>>
>> Hints
>>
>> • MacOS VMs now are signed! This should fix a lot of problems we had before.
>> • Please take note that win64 build lacks all library dependencies, and many things will not work (working on that).
>> Thanks to Fabio to help me put all the pieces together.
>>
>>
> ) > cheers,
>> Esteban
>
> Hi!
>
> Just a little feedback.
>
> Currently, at Synectique, we added Pharo 61 64bits build to our
> Jenkins. Those builds failed **a lot** because of segmentation faults.
> We added a mechanism to retry two times when there was a segfault and
> even like that we have failing builds.
>
> Since the restoration of the vms I removed the retry mechanism and I
> added a hack to use the latest Pharo 70 vm
> (http://files.pharo.org/get-files/70/pharo64-linux-latest.zip) instead
> of the stable pharo 61 vm. Since then, there was no crash due to the
> VM.
> This is a great improvement.
> Then I have a question: Is it plan to release new stable 64bit vms for
> Pharo 61? Currently, our builds are based on hacks and if no problem
> is detected with the latest vm it would greatly help stability-wise to
> have official vms that does not crash 3/5times when we load a project.
> Also, I understand it can be hard to backport vms with the resources
> of the community. :)

Why do you need to back port? Why can't you use the 7.x VM with 6.x images? The VM is intended to be backwards compatible.

>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>

CyrilFerlicot

Re: VMs build process restored

On Thu, Feb 8, 2018 at 4:29 PM, Eliot Miranda <[hidden email]> wrote:
> Hi Cyril,
>
Hi :)

>
> Why do you need to back port? Why can't you use the 7.x VM with 6.x images? The VM is intended to be backwards compatible.
>

For each Pharo release, Pharo defines stable vms.

For example, in a Jenkins bash script if we execute this:

wget -O- https://get.pharo.org/64/61+vm | bash

It will download a fresh Pharo 6.1 image, a source file and a vm of
the right OS marked as stable for Pharo 6.1. With this, we ensure that
a certain Pharo release will not have a different vm too often because
if changes are intended to be backwards compatible, there is always
the possibility a problem get through (for example one time OSProcess
stopped to work on OSX because of a problem with the system version).
So, I *can* use the vm for Pharo 7 if I get it myself but through
hacks in our scripts instead of using official distribution ways of
Pharo. I would prefer to only use official distribution ways in order
to reduce the complexity of our scripts.
In conclusion what I mean by "backport" is that Pharo officially marks
the current vm as stable for Pharo 6.1 to get it via zeroconf.

--
Cyril Ferlicot
https://ferlicot.fr