[vwnc] Image building under Linux

I've been trying to automate building my VW7.6 images under Linux but 
I'm having a problem.  If my build script closes a window such as:

Workbook allInstances do: [:each | each closeAndUnschedule].
[ObjectMemory saveAs: 'myimage' thenQuit: true] fork.

If I load a script like the above using "visual visualnc.im -filein 
script.st" then resulting image is unstable.  When it is running 
head-full I get errors like:

X11 Error:
Display:    0x0810e5a8
Serial:    0x0000008a
Major:    2
Minor:    0
XID:    0x0260006c
BadWindow (invalid Window parameter)

and the VM segfaults on image save.  Is there a proper way to do this? 

On a more general note, are there alternatives to Randy's CruiseControl 
or is this really the only tool for automating image builds in VW?

David

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

David

I cannot say for sure what the problem is, but only the
window manager process should close a window. You should
do something like;

Workbook allInstances do:
        [:each | [each closeAndUnschedule] uiEventFor: each builder window].
(Delay forSeconds: 5) wait. "You need to wait for all the windows to close"
[ObjectMemory saveAs: 'myimage' thenQuit: true] fork.

Terry
 
===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
< http://www.craftedsmalltalk.com>
===========================================================

> -----Original Message-----
> From: [hidden email] [[hidden email]] On Behalf Of C. David Shaffer
> Sent: Thursday, July 31, 2008 1:02 PM
> To: [hidden email]
> Subject: [vwnc] Image building under Linux
>
> I've been trying to automate building my VW7.6 images under Linux but
> I'm having a problem.  If my build script closes a window such as:
>
> Workbook allInstances do: [:each | each closeAndUnschedule].
> [ObjectMemory saveAs: 'myimage' thenQuit: true] fork.
>
> If I load a script like the above using "visual visualnc.im -filein
> script.st" then resulting image is unstable.  When it is running
> head-full I get errors like:
>
> X11 Error:
> Display:    0x0810e5a8
> Serial:    0x0000008a
> Major:    2
> Minor:    0
> XID:    0x0260006c
> BadWindow (invalid Window parameter)
>
> and the VM segfaults on image save.  Is there a proper way to do this?
>
> On a more general note, are there alternatives to Randy's CruiseControl
> or is this really the only tool for automating image builds in VW?
>
> David
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Alan Knight wrote:

I suspect the critical bit is the delay and forking the save. If you're running the script via command-line options like -doit, then that's running as part of the image start-up logic. You want to make sure that that startup logic has entirely finished before you save your image, and you don't really want all of that stuff on your stack (even just for the space it likely takes). And with things like closing windows that run asynchronously, you want to make sure they've entirely finished - you don't want your image saved with a window half-way through closing.

We've thought about trying to provide something more convenient when saving, but it's rather tricky. You know that the minute you define something that says "do this at the end of the startup process" that you will immediately need to make something run afterwards. The forking is what we do internally in image builds.

Does this imply that I also need a delay inside my fork block?  That is, the delay that Terry used would not permit the rest of the startup code to run assuming it is all in the same thread as is executing my -filein.  Putting a delay in the "forked save" would allow that startup logic to finish.

Generally speaking, I do not like to use Delay. I would prefer to change
the state of something or generate an event to show that everything is
done and I can now exit, or whatever.
 

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
< http://www.craftedsmalltalk.com>
===========================================================

---

From: [hidden email] [[hidden email]] On Behalf Of Alan Knight
Sent: Thursday, July 31, 2008 1:46 PM
To: C. David Shaffer; [hidden email]
Subject: Re: [vwnc] Image building under Linux
 
At 01:44 PM 7/31/2008, C. David Shaffer wrote:

Alan Knight wrote:

I suspect the critical bit is the delay and forking the save. If you're running the script via command-line options like -doit, then that's running as part of the image start-up logic. You want to make sure that that startup logic has entirely finished before you save your image, and you don't really want all of that stuff on your stack (even just for the space it likely takes). And with things like closing windows that run asynchronously, you want to make sure they've entirely finished - you don't want your image saved with a window half-way through closing.

We've thought about trying to provide something more convenient when saving, but it's rather tricky. You know that the minute you define something that says "do this at the end of the startup process" that you will immediately need to make something run afterwards. The forking is what we do internally in image builds.
Does this imply that I also need a delay inside my fork block?  That is, the delay that Terry used would not permit the rest of the startup code to run assuming it is all in the same thread as is executing my -filein.  Putting a delay in the "forked save" would allow that startup logic to finish.


Yes. In fact, that's the only delay you really need. I guess I didn't look at the proposed code closely enough. But you just need to make sure that other stuff gets a chance to finish before you do the image save.

--
Alan Knight [|], Engineering Manager, Cincom Smalltalk
[hidden email]
[hidden email]
http://www.cincom.com/smalltalk
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc