Hello,
Hello, over the weekend I made some changes to the waterfall, and you
might be interested.
1. *New FYI waterfall.*
I created a new waterfall for stuff you should not worry about after
committing. It's called the "FYI" waterfall.
It contains slaves that can turn red without closing the tree. For example:
- Chromium XP (gears)
- Webkit (V8-Latest)
- Webkit (webkit.org)
- Webkit (windows, scons)
It also contains slaves that are not ready for prime time, like Vista 64 and
Windows 7.
You can access it with this url :
http://build.chromium.org/buildbot/waterfall.fyi
I also added a link to this "experimental" waterfall on the top left corner
of the current waterfall.
It should simplify a little bit the main waterfall, and make it a little
faster to load.
Everything on the main waterfall should be green.
At this point there are 3 slaves that are red:
XP UI (purify) : seems to timeout.
Webkit Linux (dbg) : failed to compile, seems to be a problem with the
machine. Someone in the Linux team should look at it.
Modules Linux (valgrind): we have leaks. They should be added to the white
lists for now.
*2. ui-test --single-process does not turn the tree red anymore*
I removed the testing of ui tests --single-process from all the builders,
and moved them to
the FYI waterfall.
This speeds up the cycle time by at least 6-7 minutes.
You should still fix the bugs you introduce with --single-process. The
sheriffs will tell
you when it's broken, and will file a P1 bug against you.
I think overall this change will benefit most people. If you rely on
--single-process to
debug, and can't handle it being broken a little bit more often, maybe it's
a good
time to start learning how to debug with windbg. If there is a demand, I
can prepare
a techtalk for MTV googlers (and VC friends) about how to debug Chrome with
WinDbg.
*3. Faster builders*
The main Windows builders are now running on new 8-core machines with 16GB
of ram. They are crazy fast.
They can do a clobber build of the whole solution (not just chrome.exe) in
less than 8 minutes. (And this
is with Visual Studio 2005). This speeds up considerably the cycle time for
"Chromium XP", and should also
improve "Chromium Builder" and "Chromium Builder (dbg)".
The short time drawback is that these new machines are 1000 miles away from
the build slaves, so it takes a
little bit more time to push the build to these machines. I'll work on
moving the build slaves closer to the
builders early this week.
If you have any questions, let me know.
Thanks
Nicolas
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
