tardyp changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.2.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
p12tic has quit [*.net *.split]
alicef has quit [*.net *.split]
crazysim has quit [*.net *.split]
tardyp has quit [*.net *.split]
deepy has quit [*.net *.split]
koobs has quit [*.net *.split]
RP has quit [*.net *.split]
tardyp has joined #buildbot
crazysim has joined #buildbot
koobs has joined #buildbot
koobs has quit [Changing host]
koobs has joined #buildbot
deepy has joined #buildbot
alicef has joined #buildbot
p12tic has joined #buildbot
RP has joined #buildbot
_whitelogger has joined #buildbot
<RP> tardyp: I've been trying to work out why bonus_sorted.py we discussed (https://gist.github.com/tardyp/f5ba4591f1c65b5d823ef5ba1dc3f399) doesn't work as expected. Can we control the order builds start in from a sched.Triggerable() through builderNames?
<RP> tardyp: what seems to be happening is that the builds are being added one by one so the BuilderSorter only sees one new build and therefore it schedules it
<RP> tardyp: I think the code may reorder to be the order in the main builders list so I can try tweaking that
<RP> Hmm, sorting builders help either :(
<RP> I suspect it adds by builderid but hard to know for sure and it would be hard to reorder the ids in our db
lopdan has joined #buildbot
lopdan has quit [Client Quit]
lopdan has joined #buildbot
lopdan has quit [Client Quit]
lopdan has joined #buildbot
lopdan has left #buildbot [#buildbot]
kveremitz has quit [Quit: ZNC - http://znc.in]
kveremitz has joined #buildbot