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

Buildbot trac trac at buildbot.net
Sat Sep 20 09:04:17 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 juj):

 You are describing a different scenario, which does not have anything to
 do with this. On Windows, certain subprocess functions are known to hang
 when faced with too much data being printed, see
 http://bugs.python.org/issue22442 for a repro.

 Anyway, that was just a hunch since the symptoms here look identical to
 that. Sorry if that was confusing.

 The slave version was

 2014-08-24 12:27:57+0300 [-] twistd 12.2.0 (c:\Python27\python.exe 2.7.3)
 starting up.
 2014-08-24 12:27:57+0300 [-] reactor class:
 twisted.internet.selectreactor.SelectReactor.
 2014-08-24 12:27:57+0300 [-] Starting BuildSlave -- version: 0.8.7

 I have now updated twistd to latest 14.0.2.

 Since just printing less to stderr worked around the problem, I am no
 longer observing this and all subsequent steps have finished quickly and
 therefore I do not know if updating twistd might have also resolved this
 issue. Since that is a production server, I really cannot go testing that
 by reverting the workaround commit (which was an ok commit itself, as it
 toned down a lot of useless warnings from the test suite).

 Buildbot is a great project, thanks to the team for all the time spent in
 developing it!

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


More information about the bugs mailing list