[Buildbot-devel] keywords not honored

[Stefan Seefeld]

Stefan Seefeld wrote:
> Brian Warner wrote:
>>> In my master.cfg file I'm using lots of
>>>
>>> ShellCommand(name='foo', timeout=9600, command=[])
>>>
>>> However, the waterfall display doesn't show the step's 'name',
>>> but instead the command string. Also, the slaves don't see my timeout,
>>> but the default value (1200) instead, making them fail a lot.
>>>
>>> Are these known issues ? Any ways around this ?
>> That sounds like a bug.. maybe ShellCommand isn't allowing kwargs to override
>> the per-class defaults on those parameters.
> 
> Actually, I'v set up a sandbox buildbot instance locally, and there I do
> see the correct timeout value in the logs. The name is still wrong,
> though. (Any idea as to what could cause the timeout not to get
> propagated to the slave ?)

OK, so I figured out what's wrong with the 'name': A look into the code
revealed that what I want to set is the 'description' parameter, as that
is displayed on the status page. (This works fine indeed.)

I was confused because
http://buildbot.net/repos/release/docs/buildbot.html#Common-Parameters

indicates that...

"name
    the name used to describe the step on the status display..."


while it doesn't talk about the 'description' parameter at all. May be
that could be fixed ?


(Now I still need to figure out why on our compile farm the timeout
parameter doesn't propagate correctly...)


Thanks,
		Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...