Comment on attachment 465469 [details] [diff] [review] have central scheduler send sendchanges to tools master vm A few typos in there; also the lists of talos masters now require a retry count argument. I'd say set them at 1 for now.

What, you don't like the toosl team? :)

I have test-master1/test-master2 up and running now, just waiting to gets some changes pushed to them.

Comment on attachment 465539 [details] [diff] [review] have central scheduler send sendchanges to tools master vm (take 2) Need retry counts for the talos masters

Configured and connected to masters: tools-r3-fed-001 tools-r3-fed-002 tools-r3-fed64-001 tools-r3-fed64-002 tools-r3-w7-001 tools-r3-w7-002 tools-r3-xp-001 tools-r3-xp-002 tools-r3-leopard-001 tools-r3-leopard-002 tools-r3-snow-001 tools-r3-snow-002 tools-r3-w764-002 working on: tools-r3-w764-001 (having vnc connectivity issue)

Comment on attachment 467019 [details] [diff] [review] [checked in]have central scheduler send sendchanges to tools master vm (take 3) hmm, can't set the checked-in+ flag. http://hg.mozilla.org/build/buildbot-configs/rev/11cc13580196

Not done here until we get full actual tests running to completion - also there is still a blocking graph server bug.

Comment on attachment 467019 [details] [diff] [review] [checked in]have central scheduler send sendchanges to tools master vm (take 3) This patch is causing all the nagios spam in #build... are the sendchanges hanging because of firewall issues? I'm thinking about backing this out til that's resolved.

Do you have an example of the spam? I believe that the sendchanges are going though because I've gotten some successful test runs on auto tools stage.

Comment on attachment 470029 [details] [diff] [review] use ip address of tools-staging-master to fix vpn dns issue http://hg.mozilla.org/build/buildbot-configs/rev/4d9ef3285f13

These were backed out due to still timing out and causing #developers unhappiness while waiting for builds (added 10-18min waiting for sendchange). Also, continued nagios spam.

This is up and working now. Any new issues will be filed separately.