It's time to talk about the build sheriff stuff again (mentally
substitute some other word for the sheriff if it is distasteful for now).

A few people offered to help with tools. Here are some tools we could
have some improvements with (all that I could remember/think of):

* hardhat/qa/perf.py
  - This script creates the graph trend for the days results. It should
be improved so that it would be able to show more historical graphs,
ideally users could request an arbitrary time period. bear wrote the
original script, I wrote the graph parts, so talk to us if you want to
take this on.

* The functional and performance tests can hang. We would need a "dead
man's switch" in the QA lib that would exit Chandler after a timeout is
exceeded, and this would be reported as a failed test. Currently some
tests can fail in such a way that Chandler does not exit and this needs
manual intervention from the sheriff or someone else. Talk to me about this.

* A few of the unit tests do stuff over the network, and when there are
network problems the tests fail. These tests should be reworked so that
they work locally. Talk to the person who originally wrote the test.

* Improved system to alert people to build breakages. An idea that has
been floated around is to check who checked in for the current cycle
which failed, and email/SMS/IRC/AIM/... these people.

* SVN revision number next to the name on Tinderbox, perhaps also SVN
revision number in the cell that represents a build.

* Fix it so that all compiler errors are logged.

* Make it easier to locate the compiler/build/test errors in the build
logs, and/or provide other tools to locate them.

* Make an alert system if a Tbox machine is long overdue in reporting
results

* Send alerts if perf numbers regress beyond a certain treshold.

* A commit hook that does some sanity checkin on checkin comments.

* Others, please list...

Please note that for all of these you will need buy-in and review from
bear (at least), and I would like to be informed as well. That is
because bear's going to be the one maintaining these and if he's not
comfortable with the system it just won't work.


While we work on the tools we still need a human sheriff as well, and
bear and I do need help with this. So, the rotating duty. I'll be
updating the BuilSheriff wiki page and sending updated info regarding
that later.

-- 
  Heikki Toivonen


Attachment: signature.asc
Description: OpenPGP digital signature

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to