Ticket #302 (closed defect: fixed)
buildslave missing notification doesn't work for slaves missing at master startup
| Reported by: | exarkun | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.7.10 |
| Version: | 0.7.7 | Keywords: | |
| Cc: |
Description
The missing timer is only started when a slave disconnects from the master. If the master starts up and the slave never shows up, no one is ever notified.
This is trivial to fix, just factor the logic in detached which starts the missing timer into a separate function and then call the function from setBotmaster.
Change History
comment:2 Changed 4 years ago by dustin
- Status changed from new to closed
- Resolution set to fixed
commit 865abf5d98dda8ee71d64b6b700a5f5f0601f62d
Author: Dustin J. Mitchell <dustin@zmanda.com>
Date: Wed Feb 25 12:23:54 2009 -0500
(refs #302) start the missing-slave timer when buildbot starts up, so that we hear about slaves missing at startup, too
Note: See
TracTickets for help on using
tickets.
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
If it's really that simple, great!