[Buildbot-commits] [SPAM] [Buildbot] #845: P4Source with mode=copy generates timeout on Windows platform

[Buildbot]

#845: P4Source with mode=copy generates timeout on Windows platform
-------------------+--------------------------------------------------------
Reporter:  phil    |       Owner:                  
    Type:  defect  |      Status:  new             
Priority:  major   |   Milestone:  undecided       
 Version:  0.7.12  |    Keywords:  perforce timeout
-------------------+--------------------------------------------------------
 On our Windows XP buildslave the p4source with mode=copy will cause
 timeout problems. Our buildmaster is running on Centos 5.x

 The copy operation on the buildslave is executed through
 shutil.copytree(). There seem to be two problems with this implementation:
 (1) The timeout value is not reset after the copytree() has finished. Our
 perforce sync takes about 630 seconds. Right after the p4source buildstep
 the buildmaster would schedule the next step but the buildslave would
 timeout. We doubled the default timeout value to fix this problem.
 (2) Sometimes this buildstep times out completely. Is it possible the
 shutil.copytree() is also causing loss of connection with the buildmaster?
 See error output below. The additional problem is that sigkill does not
 work on windows and we basically need to reboot the buildslave to get it
 up & running again. When using mode=update we never experience this
 problem.

 error output:

 command timed out: 1200 seconds without output, killing pid 2544
 SIGKILL failed to kill process
 using fake rc=-1
 program finished with exit code -1

 remoteFailed: [Failure instance: Traceback from remote host -- Traceback
 (most recent call last):
 Failure: buildbot.slave.commands.TimeoutError: SIGKILL failed to kill
 process

-- 
Ticket URL: <http://buildbot.net/trac/ticket/845>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation