[Insight-developers] Dashboard

[Stephen R. Aylward]

Hi,

Is there a way to ensure that we get another IRIX build today? 

I think the problem is solved (gcc 3.3 and gcc 3.4 and others),  but...

Stephen


-----Original Message-----

From:  Hans Johnson <hans-johnson at uiowa.edu>
Subj:  Re: [Insight-developers] Dashboard
Date:  Thu Mar 10, 2005 9:54 am
Size:  3K
To:  "William A. Hoffman" <billlist at nycap.rr.com>,   "Stephen R. Aylward" <aylward at unc.edu>,   "Insight-developers (E-mail)" <insight-developers at itk.org>



Does any one have a spare cluster ;).

I've played with distcc http://distcc.samba.org/  a little, and it can do a
huge build very quickly.

Hans



On 3/10/05 8:38 AM, "William A. Hoffman" <billlist at nycap.rr.com> wrote:

> Perhaps we should change the continuos builds on some of the slower machines
> to not do make -i.  That way they will stop at the first error.  To get to the
> first error is usually very quick, but to build all of itk with an error in
> a key file takes a long time and produces voluminous dashboard errors.
> 
> -Bill
>  
> 
> At 09:27 AM 3/10/2005, Stephen R. Aylward wrote:
>> More info...
>> 
>> About the continuous being green - I must admit that this is not completely
>> true.  The IRIX64-CC took 6+ hours to report an error.  I submitted at noon,
>> and the error message was emailed to me after 7pm. So, even though it looked
>> green during the last several iterations, it was not.   The dashboards are
>> ordered by the time the build began, not by the time that the results were
>> generated.
>> 
>> Not to make an excuse (or maybe just a small one :) ), perhaps we need more
>> machines doing continuous builds...the current machines seem swamped.  Linux
>> CC required 11 hours to do the build.  IRIX64 required nearly 7.   I was left
>> having to make late night changes and not being able to test them on the
>> broken platforms.   So, I went to bed last night knowing that I was probably
>> going to hear from the dashboard-czar :)   I just didn't see a way around it
>> given the response time.
>> 
>> It truly was my mistake for not anticipating the longer build cycle since I
>> made so many changes.   Sorry about that.   I think it was a one-line bug
>> that IRIX found, that I didn't completely resolve yesterday, and that is now
>> fixed.
>> 
>> Sorry again,
>> Stephen
>> 
>> 
>> 
>>> At 07:52 AM 3/10/2005, Stephen R. Aylward wrote:
>>> 
>>>> Sorry about the dashboard - I truly thought I had taken care of things...
>>>> 
>>>> Had green continuous builds....
>>>> 
>>>> I will work on these...
>>>> 
>>>> Stephen
>>>> -- ===========================================================
>>>> Dr. Stephen R. Aylward
>>>> Associate Professor of Radiology
>>>> Adjunct Associate Professor of Computer Science and Surgery
>>>> http://caddlab.rad.unc.edu
>>>> aylward at unc.edu
>>>> (919) 966-9695
>>>> _______________________________________________
>>>> Insight-developers mailing list
>>>> Insight-developers at itk.org
>>>> http://www.itk.org/mailman/listinfo/insight-developers
>>> 
>>> _______________________________________________
>>> Insight-developers mailing list
>>> Insight-developers at itk.org
>>> http://www.itk.org/mailman/listinfo/insight-developers
>> 
>> -- 
>> ===========================================================
>> Dr. Stephen R. Aylward
>> Associate Professor of Radiology
>> Adjunct Associate Professor of Computer Science and Surgery
>> http://caddlab.rad.unc.edu
>> aylward at unc.edu
>> (919) 966-9695
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers
> 


_______________________________________________
Insight-developers mailing list
Insight-developers at itk.org
http://www.itk.org/mailman/listinfo/insight-developers

--- message truncated ---