Ticket #509 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

BuildFactory.addStep is not releasing spawned Process

Reported by: ipv6guru Owned by:
Priority: major Milestone: undecided
Version: 0.7.10 Keywords: sourceforge 1775006
Cc:

Description

To put things in a gist :

In the master.cfg :

1) I start a checkout 2) I add a step to invoke a service (python.exe <serviceName> 3) start a build 4) Close a service

The problem arises when I invoke the service on step 2. BuildBot (actually ShellCommand?) keeps on hanging to the started process <serviceName> , EVEN THOUGH the process is an independent pytthon process. IE, it executes (2) successfully and remains there and doesnt proceed to (3). (2) is a standalone process...BB wont proceed to the next step until it is killed.

Looking at the code, I see that Shell Command maintains an stdio that wont close until the process exits.

Ive even tried the want_stdout=0 attribute of Factory.addStep() to prevent output to be piped for THIS step to no avail.

Please help

Submitted: Nobody/Anonymous? ( nobody ) - 2007-08-16 06:03

Extra Comments ;-

The command that I'm executing, FYI is this :

f.addStep(ShellCommand?, command=['C:/Python23/python.exe', 'administer_position_service.py', 'start'], description='Start the position service script', want_stdout=0)

Change History

comment:1 Changed 4 years ago by ipv6guru

Moved from sourceforge

comment:2 Changed 4 years ago by dustin

  • Status changed from new to closed
  • Resolution set to invalid

not a bug

Note: See TracTickets for help on using tickets.