[M3devel] tinderbox failures

[Jay K]

I need(ed) to read through/understand the scripts more.
Yes, agreed, the configuration is best left alone when the preexisting cm3 is used -- which is always, now that I read it, it is copied either from lastok or last-rel. It should only be upgraded in association with cm3 being upgraded. Unless as a potshot to fix things, since the config files are fairly good and portable -- I think most of the stuff I removed was for pre-5.4 compat.
 
 
Anyway, you can see in the log all the cp commands failed, because -v is not understood.
 
 
Let's see how it goes now.
 
 
My three new ones should go better, freed /lots/ of diskspace, made sure there were .a files in the lastok hand built installs, though odd that it should matter, the tests should use the new stuff. We'll see. I think I ran one of them lastrel by accident.
 
 
- Jay



----------------------------------------
> Date: Wed, 22 Jul 2009 16:47:06 +0200
> From: wagner at elegosoft.com
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Subject: RE: [M3devel] tinderbox failures
>
> Quoting Jay K :
>
>> Some of the new ones aren't terrible:
>> LINUXLIBC6 failed the tests because it couldn't load dependent libraries.
>> PPC_LINUX ran out of diskspace.
>> SPARC32_LINUX looks ok.
>>
>>
>> The problem on SOLgnu is it doesn't see the config file.
>> Maybe my change yesterday will fix it? To always copy the config files?
>> I'm very "timezone challenged". I never know when a Tinderbox
>> run is in relation to my changes, and the changes column is no longer
>> filled in since the server crash. :(
>
> That's one of the things that just work in Hudson.
> I thought the release built was after your changes, or I wouldn't have
> sent the mail yet.
>
>> How about we move cp_config_files earlier in upgrade.sh??
>> I can try that right now..I can't test it other than
>> by watching the Tinderbox. If these are used with 5.4, hard to predict
>> the result.. Go ahead with that?
>
> I don't understand what you want to achieve with that.
> But I cannot check right now.
>
> 5.4 has just one single cm3.cfg file, and no sub dirs. I told you
> we'd need to cope with that.
>
> But then it seems to have worked for FreeBSD on Hudson:
>
> see
> http://hudson.modula3.com:8080/view/cm3/job/cm3-release-build-FreeBSD4/changes
> and
> http://hudson.modula3.com:8080/view/cm3/job/cm3-release-build-FreeBSD4/16/consoleFull
>
> which start with
>
> === 2009-07-21 23:17:10 build cm3 core in
> /ad0e/home/hudson/workspace/cm3-release-build-FreeBSD4 with last
> release /ad0e/home/hudson/work/cm3-inst/luthien/rel-5.4.0
> Critical Mass Modula-3 version 5.4.0
> last updated: 2006-10-11
> configuration:
> /ad0e/home/hudson/work/cm3-inst/luthien/current--release-build/bin/cm3.cfg
>
> I don't know if that's conclusive though...
>
> Olaf
> --
> Olaf Wagner -- elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>