<felixfontein>
I would guess that's what causing what you are observing; the first you triggered is run, and then all the others that are triggered afterwards are collapsed into a single one, so you get two runs altogether
<glogan>
Which ones run seems to be random, bit it's worth a shot
<glogan>
I have the trigger set with `alwaysUseLatest`, assumed that would be generating unique stamps
<glogan>
but I guess the docs do say that it's not sending any
<glogan>
dedeup(none) -> none :)
<glogan>
well, that worked, thank felixfontein
<glogan>
'course this may be exposed a bug in the buildbot UI lol
<glogan>
oh maybe not, nevermind
aakashja_ has joined #buildbot
aakashjain has quit [Read error: Connection reset by peer]
aakashja_ has quit [Remote host closed the connection]
aakashjain has joined #buildbot
aakashjain has quit [Remote host closed the connection]
vmeson has quit [Quit: Konversation terminated!]
mjw has quit [Killed (NickServ (GHOST command used by mark_!~mark@gnu.wildebeest.org))]