let me guess... why can that be happening... oh, I know: you are using windows!
yeah, as soon as we figure out how to gain stability of win32 slave,On 28 July 2011 17:46, Marcus Denker <marcus.denker@inria.fr> wrote:
>
> On Jul 28, 2011, at 4:38 PM, Torsten Bergmann wrote:
>
>>> I personally am completely confused about VMs. Now we have even one more :-)
>>
>> No - we do not have one more, just an updated rebranded version
>> as I did in the past to make it more Pharo like.
>>
>> On Win32 it goes like this:
>> ===========================
>>
>> A) Andreas provided the official Squeak VM on http://squeakvm.org/win32/
>> � �Last official one is 4.1.1, I just gave it a new pharo icon ("lighthouse"), name
>> � �and file ressource so one can see the VM version directly in Explorer.
>>
>> � � => unfortunately this is very outdated from 2010, no activity/response on
>> � � � �Andreas side and no new Win32 Squeak VM maintainer stepped up AFAIK
>>
>> � �Even when outdated we still use this as the standard VM in the Win32
>> � �Installer (see Pharo1.2), I will reuse this standard VM for 1.3 too.
>>
>> B) Eliot provides the fast Cog VM on http://www.mirandabanda.org/files/Cog/VM/
>> � �Last SVN revision is VM.r2474, again anything I do is building the
>> � �VM from subversion with another icon ("lighthouse with gear"), name and
>> � �a file ressource so one can see the VM version directly in Explorer.
>>
>> � �This Cog VM is also in the Win32 Pharo 1.2/upcoming 1.3 installer
>> � �so Win users can profit from Eliots work.
>>
>> After using the Win32-Installer one can (by using the different icon "lighthouse" or "lighthouse with gear") start the appropriate engine to run his image.
>>
>> I hope that we can get a better situation as soon as
>> - the standard VM "A" is built right from the newest VMMaker
>> - for "B" (the Cog VM) is either built from VMMaker or from Eliots SVN repo
>>
>
> And there is
>
> C)
>
> https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog-Win32/
>
> Which is auto-build and soon even auto-tested...
>
because right now something strange happens after week or two of
working it stops responding
and i need to contact INRIA admins and ask them to reboot/kick its ass
over and over again �:)
--
Best regards,
Igor Stasenko AKA sig.