"Fixed" in the sense it doesn't happen often, and likely requires a VM-level rather than image-level fix, yes. ;)
Cheers, Henry On 10.12.2009 21:05, Stéphane Ducasse wrote: > so this is fixed :) > lol > software.... well we have (as a community to make progress on tests, > documentation and tools to produce reliable software) > Stef > > On Dec 10, 2009, at 6:26 PM, Henrik Johansen wrote: > > >> I got it once last night, on Windows 7 RC1, updating the core image from >> 11080 to 11082(or3). >> There was a primitive failure mentioned in the error dialog, I stupidly >> closed the message to examine the log, but none had been written :/ >> >> Tried updating the same image 3 times after that, and got no crashes... >> >> Cheers, >> Henry >> >> On Dec 10, 2009, at 3:49 52PM, laurent laffont wrote: >> >> >>> Hi, >>> >>> I've also tested on XP Pro SP3, with windows installers. No errors for both >>> rc1 and alpha.. 1.1 alpha took 20mn to update to #11083. >>> >>> What is you configuration ? >>> >>> Laurent >>> _______________________________________________ >>> 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 > > > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
