I tried enabling two servers configured on the master today.

http://www.imedia2go.com/
http://drupalinchennai.com/

The servers status was listed as testing even though those servers don't resolve. There should be a check to to see if the servers exist and then a response that they couldn't be reached.

Comments

Amazon’s picture

We might want to add another state 'Offline' if the testing slave doesn't respond to a simple HTTP request.

boombatower’s picture

Currently the main idea behind the architecture is that the master never pings the clients. That way ppl can add and remove them without it caring. Since the client have to request test anyway.

Perhaps we should prune the servers on ping. If not activity in [time-period] then set to disabled.

boombatower’s picture

Status: Active » Closed (won't fix)

To ensure that we maintain a PULL architecture to all things like EC2 instances and stuff I don't think it is a good idea to ping the test clients, on a regular basis. As such I am going to "won't fix".

If we come up with something later then we can add it.