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

[Buildbot trac]

#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):

 I'm confused -- in your initial report you said "Observing the actual
 execution of the task, that step indeed took 3 hours, instead of 15
 minutes." but your last comment suggests that the actual time used was
 indeed 15 minutes.

 If your clocks are correct, then there is an (oddly precise!) 2-hour delay
 between `commandComplete` and the subsequent finish on the master.

 Lots of other stuff is going on on the master during that time, although
 it doesn't appear heavily loaded.  So it's neither hung doing something
 that would cause it to not check its incoming network data, nor so busy
 that such data might be queued up behind other data.

 That this only occurs on Windows makes me think that maybe this has to do
 with some kind of network buffering on the Windows side -- the precise
 2-hour delay seems to support this idea.

 One possible next step is to look at a wireshark dump, but that's not
 something you should be posting on a public bug tracker.

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