Hi,

This "image need a while after update" is normal.

I think it has to do with the really bad Weak* stuff... We should look at the 
fixes
that Martin von Loewis did back in end of 2007 when he visited SCG.

        Marcus

On Dec 8, 2009, at 8:46 PM, Michael Roberts wrote:

> Hi John, it was not the pharo image, but the pharo core image.  You
> can get them direct from the inria download area. This is linked off
> the pharo-project site.  11049 was an internal update so start from
> 
> http://gforge.inria.fr/frs/download.php/24763/PharoCore-1.1-11043-alpha.zip
> 
> I will do this myself just to check the test case.
> 
> thanks,
> Mike
> 
> On Monday, December 7, 2009, John M McIntosh
> <[email protected]> wrote:
>> Ah, if someone can describe the test case:
>> 
>> which I think is take a pharo 1.1 core 11049 then do update?
>> I'll see where it's hung.
>> 
>> would that be the
>> pharo1.1-11073-alphadev09.12.1.zip
>> or
>> pharo1.1-11073-alphaweb09.12.1.zip
>> 
>> from the 1.1 alpha links on the main pharo web page?
>> 
>> 
>> On 2009-12-07, at 1:33 PM, Henrik Sperre Johansen wrote:
>> 
>>> That's pretty normal, it's happened to me a lot of times, at least.
>>> If you leave if for a while, it'll starts responding again.
>>> No idea why it happens though, I glanced at the code one time it
>>> happened, but no neurons fired :/
>>> 
>>> Cheers,
>>> Henry
>>> 
>>> On 07.12.2009 21:49, Michael Roberts wrote:
>>>> Hi, I did a quick test on the 32bit version on 10.5.8.  I took a pharo
>>>> 1.1 core 11049 and told it to update from the network.  It processed
>>>> all the updates (took some time) and drew the "ok" dialog.  However it
>>>> then hung. I am not sure if that is related to the VM or not.  in a
>>>> spare moment I will dig deeper.
>>>> 
>>>> thanks,
>>>> Mike
>>>> 
>>>> On Fri, Dec 4, 2009 at 7:33 PM, John M McIntosh
>>>> <[email protected]>  wrote:
>>>> 
>>>>> On 2009-12-04, at 4:30 AM, Stéphane Ducasse wrote:
>>>>> 
>>>>> 
>>>>>>> john needs beta testers....Do not forget
>>>>>>> I know that we are all terribly busy.
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> Yes , *cough* feedback and response has been zero...
>>>>> Maybe I should push the self-destruct button on the 3.x, 4.x VM series.
>>>>> Where is that red button? Must be here somewhere in the office clutter...
>>>>> 
>>>>> --
>>>>> ===========================================================================
>>>>> John M. McIntosh<[email protected]>     Twitter:  
>>>>> squeaker68882
>>>>> Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
>>>>> ===========================================================================
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Pharo-project mailing list
>>>>> [email protected]
>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>> 
>>>>> 
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [email protected]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>> --
>> ===========================================================================
>> John M. McIntosh <[email protected]>   Twitter:  squeaker68882
>> Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
>> ===========================================================================
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to