[Buildbot] #3567: buildbot nine master trigger traceback in old 'slave'

[Buildbot trac]

#3567: buildbot nine master trigger traceback in old 'slave'
------------------------+-----------------------
Reporter:  tardyp       |       Owner:  tardyp
    Type:  enhancement  |      Status:  assigned
Priority:  major        |   Milestone:  0.9.0
 Version:  master       |  Resolution:
Keywords:               |
------------------------+-----------------------

Comment (by rutsky):

 This is harmless traceback: master tries to call `getWorkerInfo()` and
 falls back to `getSlaveInfo` if former is not available.

 I missed that the traceback will arise in this use case, and having
 tracebacks during normal operation is pretty bad behavior.

 Initially I wanted to not include *any* "slave" handling in `buildbot-
 worker`, but I don't see any other way to detect which version of
 slave/worker is used without actually calling
 `getSlaveInfo`/`getWorkerInfo`, also I don't see any option to silence
 traceback without patching worker, so I assume suggested by Pierre
 approach with handling `getSlaveInfo` in `buildbot-worker` is best way to
 handle this issue.

--
Ticket URL: <http://trac.buildbot.net/ticket/3567#comment:4>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation