[Buildbot] #2901: Finished time of a build step does not match the elapsedTime of the same step.

Buildbot trac trac at buildbot.net
Fri Sep 19 12:54:41 UTC 2014


#2901: Finished time of a build step does not match the elapsedTime of the same
step.
-------------------+--------------------
Reporter:  juj     |       Owner:
    Type:  defect  |      Status:  new
Priority:  major   |   Milestone:  0.9.0
 Version:  0.8.8   |  Resolution:
Keywords:          |
-------------------+--------------------

Comment (by dustin):

 The subprocess notes you see are not about a broken implementation --
 they're warnings to users not to write broken code.  The idea is that if
 you are running a subprocess which takes input from stdin and produces
 output to stdout, and you try to stuff all of the input in before reading
 any of the output, you may end up waiting for the subprocess to read()
 your input while the subprocess is waiting for you to read() its output.
 So in this case the deadlock is permanent, at least until something kills
 one of the processes.  The solution is to interleave reading output and
 writing input -- and Twisted does just that.  So I don't think that's
 quite the bug you're looking for, but I think it's close.

 The timing changes you see suggest we're dealing with a Twisted issue, as
 we use `reactor.spawnProcess` to spawn the process.  So, a simple thing to
 check is: are you using the latest Twisted (14.0.x) on the slave?

--
Ticket URL: <http://trac.buildbot.net/ticket/2901#comment:11>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation


More information about the bugs mailing list