To turn the Valgrind builds into something we can use to force someone to back their broken crap out of our nice tree, we need to have them running on the tryserver. I'm on the fence about whether it should be in trychooser, but I think it's probably more reasonable not to put it there, to just treat it as yet another flavor of Linux build and do it whenever linux or linux64 is being built.
In the case we proceed with this can we avoid linux64 until we have more machines?
I'll try to look into this in the next couple weeks, at least for linux.
This is not something I have time for in this coming quarter. If possible, we might be able to get one of our summer interns to tackle it.
What's involved with getting Valgrind runs onto the try server? I'm working on getting the valgrind runs on tbpl green, and not being able to experiment via try is a real pain. For example, I'm currently working on bug 940069, in which I need to work out if the CC is running during shutdown. If Valgrind was available on try I could easily push a patch with some debugging print statements in it. But because it's not I'm limited to things that are reasonable to land on mozilla-central.
This bug is subsumed by bug 801955.