aakashjain has quit [Read error: Connection reset by peer]
aakashjain has joined #buildbot
aakashjain has quit [Ping timeout: 268 seconds]
aakashjain has joined #buildbot
aakashjain has quit [Ping timeout: 260 seconds]
aakashjain has joined #buildbot
aakashjain has quit [Ping timeout: 250 seconds]
aakashjain has joined #buildbot
mjw has quit [Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))]
wielaard is now known as mjw
mark_ has joined #buildbot
aakashjain has quit [Remote host closed the connection]
aakashjain has joined #buildbot
rburton has quit [Read error: Connection reset by peer]
rburton has joined #buildbot
aakashjain has quit [Remote host closed the connection]
aakashjain has joined #buildbot
aakashjain has quit [Ping timeout: 250 seconds]
aakashjain has joined #buildbot
mjw has quit [Killed (NickServ (GHOST command used by mark_!~mark@gnu.wildebeest.org))]
mark_ is now known as mjw
wielaard has joined #buildbot
<aakashjain>
dol-sen: I tried multi-master buildbot on kubernetes. Stopping the master results in ongoing build being marked as RETRY immediately and schedule from start on another master. Ongoing build isn't able to move to other masters gracefully.
<aakashjain>
@tardyp do you know if buildbot multi-master has been tested on kubernetes?
aakashjain has quit [Remote host closed the connection]