Updates:
Owner: [email protected]
Comment #6 on issue 11758 by [email protected]: should track buildbot
build/test/cycle times in performance graphs
http://code.google.com/p/chromium/issues/detail?id=11758
We've been tracking build times of all targets, both full rebuilds and null
everything
up-to-date times, for Linux and Windows:
http://build.chromium.org/buildbot/perf/dashboard/targets.html
(That dashboard takes a while to load; it's pulling down a lot of graphs.)
The test verifies that the null build reports everything up-to-date, so we
can detect
if a dependency problem has been introduced in specific targets. (I hadn't
looked in
a while, it turns out the test needs to recognize that app_id runs every
time.)
Mac is only waiting on the availability of a system to run the build.
It's only doing Debug, not Release. If we wanted to do Release as well,
we'd just need
an additional set of systems to run the builds.
This is without /mp, and without Incredibuild. My gut says Incredibuild
would
introduce too much variability into the data.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
