Graph of test run times

Sep 09 14:38:11 <flacoste> mwhudson: still there?
Sep 09 14:47:49 <mwhudson> flacoste: yeah
Sep 09 14:48:10 <flacoste> mwhudson: want to chat briefly about graphs?
Sep 09 14:48:41 <mwhudson> flacoste: just having lunch
Sep 09 14:48:49 <mwhudson> irc is ok, but skype would be interfered with
Sep 09 14:49:06 <mwhudson> flacoste: i played with cprov's bbot thingy but didn't understand it at all
Sep 09 14:49:09 <mwhudson> flacoste: what do you have?
Sep 09 14:49:17 <flacoste> mwhudson: a completely rewritten system
Sep 09 14:49:29 <flacoste> mwhudson: doesn't share much with the initial concept
Sep 09 14:49:45 <flacoste> mwhudson: it tracks revision information, builder information, test runtime
Sep 09 14:49:48 <flacoste> no graph yet
Sep 09 14:49:57 <flacoste> but all the info is in the DB
Sep 09 14:50:09 <mwhudson> flacoste: same idea, talks to buildbot shoves info into a db?
Sep 09 14:50:10 <flacoste> i did graph things for my presentation by connection the SQLite DB in OO
Sep 09 14:50:15 <flacoste> yep
Sep 09 14:50:24 <mwhudson> flacoste: for graphing, surely we should use lpstats.c.c?
Sep 09 14:50:24 <flacoste> but more comprehensive
Sep 09 14:50:29 <flacoste> not sure
Sep 09 14:50:33 <mwhudson> flacoste: ok cool, where is it?
Sep 09 14:50:39 <flacoste> on my desktop
Sep 09 14:50:51 <flacoste> i can put create a project and push the branch to it
Sep 09 14:50:57 <flacoste> or i can push it to +junk
Sep 09 14:51:04 <mwhudson> just +junk for now will be fine
Sep 09 14:51:04 <flacoste> and you can take it from there
Sep 09 14:51:11 <flacoste> ok, i'll push to junk now
Sep 09 14:51:12 <mwhudson> (if you're happy with it being public)
Sep 09 14:51:14 <mwhudson> thanks
Sep 09 14:53:57 <flacoste> mwhudson:
Sep 09 14:53:58 <flacoste> lp:~flacoste/+junk/lp.buildstats
Sep 09 14:53:59 <flacoste> Created new branch.
Sep 09 14:54:35 <mwhudson> flacoste: thanks
Sep 09 14:54:43 <flacoste> mwhudson: there is also ~launchpad/lazr-source-dependencies/download-cache/
Sep 09 14:55:10 <flacoste> mwhudson: which is the branch to manage the download-cache for lazr stuff, only used by this branch for now
Sep 09 14:55:41 <flacoste> mwhudson: check that one out to download-cache in the branch and then it's the usual buildout dance: python2.5 bootstrap.py;
bin/buildout
Sep 09 14:55:53 <flacoste> mwhudson: i can give you my DB, it's mostly up to date
Sep 09 14:56:31 <mwhudson> flacoste: that'd be good, thanks
Sep 09 14:56:50 <flacoste> mwhudson: devpad:~flacoste/bbot.db.gz
Sep 09 14:57:04 <flacoste> mwhudson: put it in the top-level branch directory and gzip -d it
Sep 09 14:57:18 <flacoste> mwhudson: we can talk tomorrow about it once you had a look at it

Hello Francis,

What are the next steps for getting this done?

jml

* Deploy lp:~flacoste/+junk/lp.buildstats on devpad to be run periodically to maintain the DB up to date. (Probably as part of the lp-qa-team crontabs).

* Make sure that the test do include the per-test timing data.

* Add the code to graph the data (or hook it up into pgmetrics).

I don't have the cycles to do this before next year.

See also http://code.mumak.net/2010/11/boiling-kettles-unit-tests-and-data.html

The trick is having an auto-updating graph. It's easy to turn a subunit run into a number.

Like, say, <https://lpstats.canonical.com/graphs/LPBuildSystemAverageBuildTime/>.