[M3devel] Tinderbox/Hudson

[Jay K]

I don't think that is it but I don't know. I don't know the various paths through the scripts, haven't studied them enough.. for some reason my one run on SOLgnu did run the tests and turned green. Most of my runs stop after successful compile so stay yellow. I edited out that one line you said to.
Maybe I should an -x run.
 
 - Jay


----------------------------------------
> From: jay.krell at cornell.edu
> To: wagner at elegosoft.com
> CC: m3devel at elegosoft.com
> Subject: RE: [M3devel] Tinderbox/Hudson
> Date: Sun, 26 Jul 2009 09:19:42 +0000
>
>
> Looking at your Hudson jobs..to create my own.. I notice you run test_m3tests manually. I'll try that.
> Maybe of the yellow jobs ran to completion..but maybe because I didn't run test_m3tests?
>
> - Jay
>
>
>
> ----------------------------------------
>> Date: Sun, 26 Jul 2009 11:17:49 +0200
>> From: wagner at elegosoft.com
>> To: jay.krell at cornell.edu
>> CC: m3devel at elegosoft.com
>> Subject: Re: [M3devel] Tinderbox/Hudson
>>
>> Quoting Jay K :
>>
>>> - The links to my Tinderbox test results don't work.
>>>
>>> - Why are my Tinderbox status usually yellow even though the logs look ok?
>>> Due the missing test results?
>>>
>>> - I do already have Hudson server running OpenBSD/x86, that was
>>> easy, not configured yet (still cross building cm3 and will try a
>>> Tinderbox run first instead.)
>>>
>>> LINUXLIBC6 is yellow, but this looks ok:
>>>
>>> http://tinderbox.elegosoft.com/tinderbox/cgi-bin/gunzip.cgi?tree=cm3&brief-log=1248586756.14190
>>>
>>> Do they have to be more recent? Or need last release and last ok?
>>> I only do last ok. You don't have last release for AMD64_LINUX, it
>>> doesn't exist, but are green.
>>> Maybe two separate builds are needed?
>>>
>>> SPARC32_LINUX is yellow but it also looks ok.
>>> http://tinderbox.elegosoft.com/tinderbox/cgi-bin/gunzip.cgi?tree=cm3&brief-log=1248433196.25517
>>
>> Tinderbox shows running builds that haven't complete yet in yellow.
>> Results are either green, red, or orange. So the result transfer to
>> the server may have failed.
>>
>>> The most recent completed PPC_LINUX failed to get much of the source
>>> tree in the CVS checkout. That happens often. I should probably put
>>> in a retry or something..
>>
>> No. You should probably do something about your network connection ;-)
>>
>> BTW, the exit you put in after the cvs checkout won't work this way.
>> Unless you use special bash pipe result evaluation, it's always the
>> _last_ process in a pipe that determines its result code.
>>
>>> (Bringing back I386_DARWIN, funny thing there, is that to compile X
>>> client, you need Python, and the in-box one isn't new enough, and
>>> current doesn't build out of the box because it assumes a full Mac
>>> system..still working on it..)
>> --
>> 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
>>