Hi,
The number of memory tests bots has been increasing rapidly recently, and
since the main buildbot console view
was getting too big and slow, I decided to move the memory tests in their
own buildbot master. HOWEVER, this does
not indicate in any ways that they are less important.
On http://build.chromium.org you can now see a fourth line at the top
showing the status of the memory tests. Any redness there
should be considered as bad as any other redness on the main waterfall, and
the sheriff should act on it.
The memory test console is at this url :
http://build.chromium.org/buildbot/memory/console
Please take a look at this page when you commit to make sure you did not
break anything. Since these bots are slow
to cycle (some take more than 1 hour), I would suggest that you monitor
closely the main console at build.chromium.org
when you commit a change, and when you see that everything is turning green,
you should also take a look at the memory
console to make sure you did not regress this one either.
This is clearly not the most user-friendly way of doing it, but it was
essential at this point to relieve the pressure on our
main buildbot master. We are currently working on the design of a new
implementation of the console view that will
let us merge multiple buildbot masters together. This should fix that
problem. ETA unknown.
Thank you,
Nicolas
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
