[Vm-dev] VM Maker: VMMaker.oscog-eem.662.mcz

gettimothy gettimothy at zoho.com
Fri Apr 4 01:24:03 UTC 2014

Thanks Dave.

What is the path of code..starting from Eliot uploads an update to Cog or VMMaker.oscog.

Does it look like this: Eliot->source.squeak.org/VMMaker->Jenkins->SVN

Or is it something else?

More importantly, is there someplace where this is documented?



---- On Thu, 03 Apr 2014 17:11:51 -0700 David T. Lewis<lewis at mail.msen.com> wrote ---- 

On Thu, Apr 03, 2014 at 04:39:12PM -0700, gettimothy wrote: 
> David, 
> is http://build.squeak.org/job/CogVM/546/ a daily build based off the work Eliot is doing each time he uploads an update? 
> How are the Jenkins build above and http://squeakvm.org/svn/squeak/branches/Cog/ related? 
The InterpreterVM and CogVM jobs that run on build.squeak.org are jobs that test 
the overall process of loading VMMaker and various related packages needed for 
generation of VM sources from Smalltalk source code (aka "slang"). The intent is 
to verify that the source packages are loadable into a clean Squeak image, and 
that they produce a coherent set of generated sources that can be used (along with 
the platform sources that are managed in Subversion) to compile a working VM. 
It is necessary to run the compile step in order to ensure that the sources are 
really in good shape. For example, the compile step recently detected a couple 
of missing methods (the same ones that you had identified earlier by the way) 
in the oscog VMMaker package. 
Assuming that the compile step is successful, the sources are assumed to be in good 
shape, and the resulting source code is saved as the outcome of the Jenkins test. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20140403/31e0a21f/attachment.htm

More information about the Vm-dev mailing list