I'm missing my green bars...
Remy Blank
option, and I'm missing the warm fuzzy feeling that its all-green status
page was giving :-)
Any chance that we could re-activate it? Probably by emptying its build
queue beforehand?
I also have a Windows Vista VM ready for a build host.
-- Remy
Christian Boos
> Bitten has been deactivated since the "accident" with the "rebuild all"
> option, and I'm missing the warm fuzzy feeling that its all-green status
> page was giving :-)
>
> Any chance that we could re-activate it? Probably by emptying its build
> queue beforehand?
>
>
Well, it must be noted that since this deactivation, t.e.o. has not seen
any disruption, as was regularly the case before (see #8602). At least
none that I'm aware of. No "IDLE in transaction" problem either (#8443).
So unless things have improved on the Bitten side, I'm a bit reluctant
to reactivate it, in particular in days of heavy activity ;-)
> I also have a Windows Vista VM ready for a build host.
>
Windows 7 anyone? ;-)
-- Christian
Remy Blank
> So unless things have improved on the Bitten side, I'm a bit reluctant
> to reactivate it, in particular in days of heavy activity ;-)
I understand. It's pretty clear that Bitten generates lots of DB
activity, especially with ~10 build slaves polling for builds regularly
(currently every 5 minutes). This would explain #8602, but for the other
one, it's probably a bug in Bitten itself.
OTOH, I was hoping that the experience gained on t.e.o could somehow
flow back into Bitten and make it more efficient.
One thing we could already do to lighten the load on t.e.o is to avoid
running too many builds in parallel. Currently, all configurations are
built independently, hence in parallel. I could change my scripts so
that at most one build is active at any time (per platform). This should
avoid the peak of activity at every commit.
The thing is, Bitten really is incredibly useful.
> Windows 7 anyone? ;-)
Not yet, but I plan to buy a new laptop, so I should have a license
pretty soon.
-- Remy
Tim Hatch
> to reactivate it, in particular in days of heavy activity ;-)
I found my old buildbot config file and put that system back online,
running against the advanced_i18n branch of Genshi. The SVNPoller is
set to fire every 10 minutes.
http://buildbot.timhatch.com/trac/waterfall
- Ubuntu x86_64 (2.4, 2.5, 2.6)
- OS X 10.5.6 (2.4, 2.5, 2.6)
- Windows 7 (2.6)
>> I also have a Windows Vista VM ready for a build host.
>>
>
> Windows 7 anyone? ;-)
It's the only Windows I had immediately handy, so it's on there (with a
one-line change to stdlib, see Python bug 6906). If you'd like to add
to the pool, contact me off-list.
Tim
Remy Blank
> I found my old buildbot config file and put that system back online,
> running against the advanced_i18n branch of Genshi. The SVNPoller is
> set to fire every 10 minutes.
>
> http://buildbot.timhatch.com/trac/waterfall
Thanks! I feel much better already ;-)
-- Remy
Christian Boos
>> So unless things have improved on the Bitten side, I'm a bit reluctant
>> to reactivate it, in particular in days of heavy activity ;-)
>>
>
> I found my old buildbot config file and put that system back online,
> running against the advanced_i18n branch of Genshi. The SVNPoller is
> set to fire every 10 minutes.
>
> http://buildbot.timhatch.com/trac/waterfall
>
Cool! Is this buildbot going to stay for a while?
If so, I'd like to link to it from some TracDev page, if you don't mind.
-- Christian
Tim Hatch
>>
>
> Cool! Is this buildbot going to stay for a while?
> If so, I'd like to link to it from some TracDev page, if you don't mind.
Yes, the buildmaster will live there indefinitely. I've updated the
TracDev/AutomatedBuilds wiki page to mention this location, and feel
free to adjust others.
Tim