[Buildbot] #2391: ShellCommand(description=...) doesn't take effect until command starts
Buildbot trac
trac at buildbot.net
Sat Jun 14 15:49:47 UTC 2014
#2391: ShellCommand(description=...) doesn't take effect until command starts
------------------------+--------------------
Reporter: dank | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: 0.8.+
Version: 0.8.7 | Resolution:
Keywords: |
------------------------+--------------------
Changes (by Jc2k):
* milestone: 0.8.9 => 0.8.+
Old description:
> When I have a bunch of ShellCommand steps, looking at the
> build status early on is rather uninformative; it says
> 1. shell
> 2. shell_1
> 3. shell_2
>
> Only after they complete is the description used, e.g.
>
> 1. shell install_deps ( 31 secs )
> 2. shell_1 configure ( 1 secs )
> 3. shell_2 compile ( 0 secs )
>
> Calling self.step_status.setText(self.describe(step_status.isFinished()))
> in setStepStatus() seems to make the description show up when
> I want it.
New description:
When I have a bunch of ShellCommand steps, looking at the
build status early on is rather uninformative; it says
1. shell
2. shell_1
3. shell_2
Only after they complete is the description used, e.g.
1. shell install_deps ( 31 secs )
2. shell_1 configure ( 1 secs )
3. shell_2 compile ( 0 secs )
Calling self.step_status.setText(self.describe(step_status.isFinished()))
in setStepStatus() seems to make the description show up when
I want it.
--
--
Ticket URL: <http://trac.buildbot.net/ticket/2391#comment:2>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the bugs
mailing list