verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
flx[m] has quit [Ping timeout: 260 seconds]
glogan has quit [Ping timeout: 256 seconds]
cognifloyd has quit [Ping timeout: 248 seconds]
glogan has joined #buildbot
cognifloyd has joined #buildbot
flx[m] has joined #buildbot
glogan has quit [Ping timeout: 240 seconds]
flx[m] has quit [Ping timeout: 250 seconds]
flx[m] has joined #buildbot
glogan has joined #buildbot
<glogan> Am I out to lunch, or does ShellSequence not support a timeout? http://docs.buildbot.net/latest/manual/configuration/steps/shell_sequence.html
<glogan> I had a runaway build today that got stuck for 7+ hours... I have timeout set but it no worky
<tardyp> you have to configure it in the ShellArg
<tardyp> apparently not :(
<glogan> Hence my confusion!
<glogan> It's not documented, so I'm not sure if it's a bug or not haha
<glogan> I'd expect it to be in one of those, but it's not
Foxboron has joined #buildbot
<Foxboron> Yoo, I'm making Force Scheduler which takes a json endpoints and schedules N builds based on some package names. I'm trying to use step.Trigger to launh these builds. But when I just to try launch them with a simple for loop everything seems to stall
<Foxboron> I'm also unable to restart the master :/