<jmd>
okay to the log file says "Connection was refused by other side: 111: Connection refused." But sending manually from the buildbot account, mail goes through just fine. Can I make the log a bit more explicit, so I can see the SMTP transaction?
<jmd>
mattock: How dod you configure it to use a local MTA? I don't see an option for that?
<mattock>
if you just leave out the SMTP settings then it will default to localhost:25
<jmd>
Okay, my bad. Typo in master.cfg file!
sknebel has quit [Remote host closed the connection]
sknebel has joined #buildbot
<mattock>
jmd: +1
jmd has quit [Remote host closed the connection]
Guest5805 is now known as mjw
jmd has joined #buildbot
<jmd>
I have noticed that when I push a set of commits buildbot always builds the first commit, and then the last. Why is this? How can I configure it so that it only builds the most recent commit?
<dol-sen>
add a delay?
<dol-sen>
then check if that commit is still latest
dol-sen has quit [Changing host]
dol-sen has joined #buildbot
<jmd>
But I thought that git push was atomic ?
<jmd>
And I'm using a polling scheduler, so there's an implicit delay there anyway.
<dol-sen>
I'm getting too out of touch with latest buildbot code and use
<sknebel>
I assume setting up a tiny timer would help, becuase presumably the poller goes through the commits and in the tiny time because the first and later commits being emitted the scheduler already has set thefirst off
<sknebel>
so just set like 1 second or 5 seconds and see what happens
<jmd>
I will try it.
<jmd>
But I can't imaging why the poller would iterate through commits. The most reasonable thing would be for it to just fetch the HEAD.
<dol-sen>
there are many reasons such as running various checks on a per commit basis