[Glass] [ANN] GsUpgrader

[Johan Brichau via Glass]

Jon, 

Just to be sure: a logout is not sufficient. You must exit the topaz session and restart topaz.
The issue is unaffected by the memory used by topaz, it is because the memory used by external processes (curl downloads).

Johan

On 22 Sep 2014, at 19:50, Jon Paynter <kittle31 at gmail.com> wrote:

> Dale,
> Glad to hear you found the problem.
> 
> i suspect what im seeing is different.  initially I was getting an error when running #upgradeGLASS1, so based on Johan's report of out of memory, I ran the various parts individually, with a commit and logout in between.
> 
> #upgradeGrease --> no problems
>   it also ran #upgradeMetacello with no problems.
> 
> But when I run #upgradeGLASS1, I get this:
> --transcript--'Loading baseline of BaselineOfGrease...'
> --transcript--'Project: System-Digital-Signatures stable'
> --transcript--' [0.243]'
> --transcript--'Project: SMTPMail stable'
> --transcript--'Project: UTF8 stable'
> --transcript--'...finished baseline'
> --transcript--'No instance migrations performed.'
> ERROR 2003 , a OffsetError occurred (error 2003), reason:objErrBadOffsetIncomplete, max:0 actual:1 (OffsetError)
> topaz 1>
> 
> As per your suggestion, I logged out of topaz and re-ran, But I get the same error.
> This is running on the default gemstone configurations, so GEM_TEMPOBJ_CACHE_SIZE=50000KB, and the VM has 1GB of memory.
> 
> If there are any other logs you would like to see, let me know.
> 
> 
> 
> On Mon, Sep 22, 2014 at 10:24 AM, Dale Henrichs via Glass <glass at lists.gemtalksystems.com> wrote:
> Johan,
> 
> The bug that you reported does indeed produce the error signature that you reported earlier and is likely to be the root cause of Jon's problems as well ...
> 
> I have a couple of open bugs against Metacello about the poor error messages for retry[1] and poor error reporting during github downloads[2] that I was about to address today:) so the timing is good.
> 
> Right now I still am a bit mystified about why I am not seeing the errors caused by "Cannot allocate memory", but now that I know what to look for, I should be able to figure it out ...
> 
> So thanky Jon and Johan for your patience and help ferreting this puppy out!
> 
> Dale
> 
> [1] https://github.com/dalehenrich/metacello-work/issues/227
> [2] https://github.com/dalehenrich/metacello-work/issues/226
> 
> On Mon, Sep 22, 2014 at 7:39 AM, Johan Brichau via Glass <glass at lists.gemtalksystems.com> wrote:
> 
>> Johan,
> 
> @Dale: this time, it wasn’t me, it was Jon :)
> 
>> I have been trying a whole bunch of combinations to try to reproduce the conflict that you are seeing and I've been unsuccessful ... so I guess I need additional information. 
> 
> Jon, I just ran into an issue which I suspect you are seeing as well [1].
> For me to confirm, could you repeat these steps and see if it works:
> 
> - when the error happens, exit from topaz
> - login to topaz again and launch the same upgrade expression
> 
> -> does it work?
> 
> If yes, then it is the same issue as the one in [1]. Otherwise, can you keep an eye on the memory consumption of your box (using top/htop) while running the upgrade script? And what amount of memory is available on your box?
> 
> Johan
> 
> [1] https://github.com/GsDevKit/gsUpgrader/issues/5
> 
> 
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
> 
> 
> 
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140922/8f9955ac/attachment-0001.html>