New joyride build 131

[Bert Freudenberg]

I just re-reran it and it picked up those builds fine. I suspect a  
race - it detects the new build directory, but the log is not up yet.  
I'll see if I can avoid the race ...

- Bert -

On Oct 28, 2007, at 21:49 , Michael Stone wrote:

> Bert,
>
> Builds joyride-129 and joyride-131 look finished to me but your script
> reported them as failed.
>
> This is probably due to changes that I made recently (#4251 and #4253)
> but I don't know enough about how your script works to be certain.
>
> Do you have any ideas on what's going on?
>
> Michael
>
> P.S. - Mitch - we were firing off builds frequently today because  
> Scott
> and I made fairly significant implementation changes over the last two
> days that, unfortunately, did not work when run in the environment
> provided by cron.
>
> The new implementation of the dropbox scanner seems to be functioning
> correctly now, so we should be back to our regularly scheduled
> programming. (no pun intended, of course :)
>
>
>
>
> On Sun, Oct 28, 2007 at 09:38:42PM +0100, Bert Freudenberg wrote:
>>
>> On Oct 28, 2007, at 21:34 , Bernardo Innocenti wrote:
>>
>>> Mitch Bradley wrote:
>>>
>>>> Perhaps we should reconsider the wisdom of hourly builds, or quit
>>>> sending hourly change reports, or something.
>>>
>>>
>>> ...or not running new builds unless the datestamps of the source
>>> directories say something has changed?
>>
>> I thought that was the case?
>>
>>> But anyway, I always wanted some way to do "I want a build now"
>>> so I don't have to wait 30" on average to see if my changes work.
>>
>> Anyway, I changed the mail notifications to not send out a message
>> for failed builds for now.
>>
>> - Bert -
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/devel