[Glass] Seaside Smalltalk-CI build for Gemstone runs out of temp object space

[Dale Henrichs via Glass]

This looks the first use-case for adding GemStone specific options to 
the .smalltalk.ston file[1].

I would imaging that I would add something like an 
SCIGemStoneConfiguration class that would have options for 
GEM_TEMPOBJ_CACHE_SIZE or perhaps a relative path to the gem.conf would 
be better ...

It looks like builderCI uses a default GEM_TEMPOBJ_CACHE_SIZE of 100M[2]...

Adding a new SCIGemStoneConfiguration class and starting off with two 
new options: gem.conf and system.conf seems to me to be the right path ...

The .smalltalk.ston file would look something like this with the new 
options (subject to discussion with Fabio):

SmalltalkCISpec {
   #gemstone:
     SCIGemStoneConfiguration {
       #gemConfPath : 'tests/gemstone/gem.conf',
       #stoneCofPath : 'tests/gemstone/system.conf'
     }
   #loading : [
     SCIMetacelloLoadSpec {
       #baseline : 'Seaside3',
       #directory : 'repository',
       #load : [ 'CI' ],
       #platforms : [ #pharo ]
     },
     SCIMetacelloLoadSpec {
       #baseline : 'Seaside3',
       #directory : 'repository',
       #load : [ 'Tests' ],
       #platforms : [ #squeak ]
     },
     SCIMetacelloLoadSpec {
       #baseline : 'Seaside3',
       #directory : 'repository',
       #onWarningLog : true,
       #load : [ 'CI' ],
       #platforms : [ #gemstone ]
     },
     SCIMetacelloLoadSpec {
       #baseline : 'Seaside3',
       #directory : 'repository',
       #onWarningLog : true,
       #load : [ 'ALL' ],
       #platforms : [ #gemstone ]
     }
   ]
}

Do you think this would work for you? Any other ideas?

As a side note, I anticipate that the smalltalkCI .smalltalk.ston file 
will find a place within GsDevKit_home as both a way of specifying 
default attributes (system.conf and gem.conf patchs) for creating stones 
as well as supporting scripts for launching .smalltalkCI-based local 
test runs, so the things we define here could very easily find their way 
into usage for GsDevKit_home beyond running travis tests ...

Dale

[1] https://github.com/hpi-swa/smalltalkCI#complete-smalltalkston-template
[2] 
https://github.com/dalehenrich/builderCI/blob/master/build_gemstone.sh#L193

On 03/28/2016 01:35 AM, Johan Brichau via Glass wrote:
> Hi there,
>
> The Seaside Travis build using Smalltalk-CI runs out of temp object 
> space [1].
> The travis log does not mention much, but a local run of the 
> Smalltalk-CI build confirmed me this is the case after examining the 
> gemnetobject log file.
>
> What would be the way to raise the GEM_TEMPOBJ_CACHE_SIZE for the GS 
> environment in these builds?
> I guess this first requires to be able to setup a GsDevKit stone with 
> a custom GEM_TEMPOBJ_CACHE_SIZE parameter? Or can we pass this to the 
> `serverDoit` command in Tode?
>
> Johan
>
> [1] https://travis-ci.org/SeasideSt/Seaside/builds/118681121
>
>
> _______________________________________________
> 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/20160328/d623ed2b/attachment.html>