#802: Early Timeouts
-------------------+--------------------------------------------------------
Reporter: axel | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.2
Version: 0.7.12 | Keywords:
-------------------+--------------------------------------------------------
Comment(by dustin):
I can't see how this would happen without some badly-behaved clocks.
{{{RunProcess._startCommand}}} sets {{{self.startTime}}} and sets up the
timeout at the same time:
{{{
self.startTime = util.now(self._reactor)
...
self.timer = self._reactor.callLater(self.timeout, self.doTimeout)
}}}
{{{doTimeout}}} prints {{{self.timeout}}}'s value:
{{{
command timed out: 1200 seconds without output, killing pid 6908
}}}
And the elapsed time (219.410117) is later calculated in {{{finished}}}:
{{{
self.elapsedTime = util.now(self._reactor) - self.startTime
}}}
The overall order of events, then, is:
* record startTime
* start 1200s timer
* 1200s timer expires
* calculate elapsedTime
Note that the 1200s is embedded *inside* the 219s elapsed time.
Do you have the twistd.log from this (or a similar) failure?
--
Ticket URL: <http://buildbot.net/trac/ticket/802#comment:9>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
