Originally, the try server slaves were all configured to do builds. We've since made changes to the ref images, and m-c build slaves, so that they can do builds *and* unittests. We need to make the same changes here in the try server slaves.

fyi: Aki is adding new try server slaves in bug#463340, which will do both builds and unittests. We need to make the same changes to the pre-exiting try server build slaves. A quick look through inventory shows the following machines being used by tryserver in one form or another: build (staging) =============== staging-try-master staging-try1-linux-slave staging-try1-win32-slave build (production) ================== try-master bm-xserve15 try1-linux-slave try1-win32-slave try2-linux-slave try2-win32-slave try-linux-slave03 try-win32-slave03 talos? ====== qm-ptiger-try01 qm-pubuntu-try01 qm-pxp-try01 dedicated unittest machines? ============================ try-pmac-unit-01 try-unit-linux-01 try-unit-linux-02 try-unit-win32-01

Just to comment on what has already happened. Over weekend, in support of getting 445611 bhearsum and nthomas made a couple of changes to the windows staging-try slave for me to get unit tests running. The changes were: Installing mercurial Coping across d:\Utilities for pskill Setting the group policy to allow remote desktop connections at 24-bit colour. The linux staging-try slave didn't need to have any real changes done, I just had to start Xvfb and set the DISPLAY correctly for the cltbld user.

Talked to Aki, and assigning to him, as he's already looking at this area in other bugs...

I believe this is resolved since I've replaced every try slave except for the xserve with newly imaged boxes.