When using 'p4.run("sync","//PATH/...") the Windows 10 slave drops the connection after 5 minutes every time. This was proven on a Webex using Wireshark.
If 'p4sync()' is used the command ran to completion (20 minutes). Potentially there is a problem with P4Groovy commands not displaying any output till the end of the command that is triggering this problem.
This ticket has been created to record the occurrence, allow me to try and reproduce the problem and to be a place holder where other reports of the same problem can be recorded.
Note: Cloudbees support were unable to find a problem on their side.
Example jenkinsfile (in editor):
pipeline{
agent{
label 'Win10'
}
stages{
stage('P4 Sync'){
steps{
script{
def p4 = p4 credential: 'MasterCredential', workspace: manualSpec(charset: 'utf8', name: 'CLIENT', pinHost: false, spec: clientSpec(allwrite: true, backup: false, clobber: false, compress: false, line: 'WIN', locked: false, modtime: false, rmdir: false, streamName: '', type: 'WRITABLE', view: '//depot/... //CLIENT/...'))
p4.run("sync","-f", "//depot/PATH/...#0")
p4.run("sync","-f", "//depot/PATH/...")
}
}
}
}
}
- is duplicated by
-
JENKINS-55209 p4 groovy commands with 300 second timeout
-
- Closed
-
- relates to
-
-
- Open
-
[JENKINS-58161] Agent time out with P4Groovy sync after 5 minutes?
Karl Wirth
created issue -
Karl Wirth
made changes -
| Assignee | New: Karl Wirth [ p4karl ] |
Karl Wirth
made changes -
| Description |
Original:
When using 'p4.run("sync","//PATH/...") the Windows 10 slave drops the connection after 5 minutes every time. This was proven on a Webex using Wireshark. If 'p4sync()' is used the command ran to completion (20 minutes). Potentially there is a problem with P4Groovy commands not displaying any output till the end of the command that is triggering this problem. This ticket has been created to record the occurrence, allow me to try and reproduce the problem and to be a place holder where other reports of the same problem can be recorded. +Note:+ Cloudbees support were unable to find a problem on their side. |
New:
When using 'p4.run("sync","//PATH/...") the Windows 10 slave drops the connection after 5 minutes every time. This was proven on a Webex using Wireshark. If 'p4sync()' is used the command ran to completion (20 minutes). Potentially there is a problem with P4Groovy commands not displaying any output till the end of the command that is triggering this problem. This ticket has been created to record the occurrence, allow me to try and reproduce the problem and to be a place holder where other reports of the same problem can be recorded. +Note:+ Cloudbees support were unable to find a problem on their side. Example jenkinsfile (in editor): {code:java} pipeline{ agent{ label 'Win10' } stages{ stage('P4 Sync'){ steps{ script{ def p4 = p4 credential: 'MasterCredential', workspace: manualSpec(charset: 'utf8', name: 'CLIENT', pinHost: false, spec: clientSpec(allwrite: true, backup: false, clobber: false, compress: false, line: 'WIN', locked: false, modtime: false, rmdir: false, streamName: '', type: 'WRITABLE', view: '//depot/... //CLIENT/...')) p4.run("sync","-f", "//depot/PATH/...#0") p4.run("sync","-f", "//depot/PATH/...") } } } } } {code} |
Karl Wirth
made changes -
| Labels | New: P4_VERIFY |
Karl Wirth
made changes -
| Assignee | Original: Karl Wirth [ p4karl ] |
Karl Wirth
made changes -
| Link |
New:
This issue is duplicated by |
Karl Wirth
made changes -
| Rank | New: Ranked higher |
Karl Wirth
made changes -
| Rank | New: Ranked lower |
I wanted to add that this issue also occurs when running a p4groovy.run integrate command.
> def integrateResults = perforce.run("integ", "-c${changeListNum{color}}", "//${SOURCE_BRANCH{color}}/...", "//${TARGET_BRANCH{color}}/...")
The merge lasts longer than 5 minutes because there are so many files to integrate, and, as a result, the build process is aborted.
If we can change that hard-coded timeout to a setting that we can modify, that would be ideal. Until then, my current workaround is to call a bat script that calls p4 integ.
Jonathan Hurtado
added a comment - - edited I wanted to add that this issue also occurs when running a p4groovy.run integrate command.
> def integrateResults = perforce.run( "integ" , "-c ${ changeListNum{color}}" , "// ${ SOURCE_BRANCH{color}}/..." , "// ${ TARGET_BRANCH{color}}/..." )
The merge lasts longer than 5 minutes because there are so many files to integrate, and, as a result, the build process is aborted.
If we can change that hard-coded timeout to a setting that we can modify, that would be ideal. Until then, my current workaround is to call a bat script that calls p4 integ. 
I'm running into this variation when running P4Groovy:
It times out after 30 seconds if there's no output because of this hard-coded beauty:
https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Request.java:171
// wait until the response arrives
t.setName(name+" / waiting for "channel.getName()" id="+id);
while(response==null && !channel.isInClosed())
// I don't know exactly when this can happen, as pendingCalls are cleaned up by Channel,
// but in production I've observed that in rare occasion it can block forever, even after a channel
// is gone. So be defensive against that.
wait(30*1000);
if (response==null)
// channel is closed and we still don't have a response
throw new RequestAbortedException(null);