[JIRA] (JENKINS-40355) P4 hangs on reconcile call
Title: Message Title Brian Collum commented on JENKINS-40355 Re: P4 hangs on reconcile call Hey Matthew Smith, no we never resolved it per se. But we have not actually run into this since I entered this ticket. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40355) P4 hangs on reconcile call
Title: Message Title Brian Collum created an issue Jenkins / JENKINS-40355 P4 hangs on reconcile call Issue Type: Bug Assignee: Unassigned Attachments: jenkins.p4crash.dump Components: p4-plugin Created: 2016/Dec/10 12:33 AM Environment: Windows 10 Pro 64-bit Jenkins 2.19.4 P4-Plugin 1.4.10 java version "1.8.0_111" Java(TM) SE Runtime Environment (build 1.8.0_111-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode) Priority: Critical Reporter: Brian Collum It seems the p4 plugin is simply hung on this p4 command. This is the second time it has happened, the first time was probably about two months ago (don't have logs from that time). We usually have at least one build occur every day, if not multiple. So it seems very infrequent but when it does happen, hitting the 'x' to cancel the build does not affect it and that Jenkins executor stays hung. So my only course of action that I know of is to kill the Jenkins service and restart it. Here is the last output on the Jenkins console: P4 Task: reverting all pending and shelved revisions. ... p4 revert C:\Jenkins\jobs\Sepac_x.58\workspace\buildType\standard\osType\linux\spec___ - p4 revert C:\Jenkins\jobs\Sepac_x.58\workspace\buildType\standard\osType\linux\specialBuild\none/... C:\Jenkins\jobs\Sepac_x.58\workspace\buildType\standard\osType\linux\specialBuild\none/... - file(s) not opened on this client. ... rm
[JIRA] [perforce-plugin] (JENKINS-28465) WSAECONNRESET failure on sync causes build to be marked as failed
Title: Message Title Brian Collum commented on JENKINS-28465 Re: WSAECONNRESET failure on sync causes build to be marked as failed I guess I would expect it to possibly retry the connection again? Or mark the possibly mark the build as ABORTED or something similar (though I see why from your standpoint you may not want to do that). Either way, thanks for the help. We have been searching for the source of the problem but none of our developers have seen a issue. Only our Jenkins instance gets errors like this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-28465) WSAECONNRESET failure on sync causes build to be marked as failed
Title: Message Title Brian Collum closed an issue as Not A Defect Jenkins / JENKINS-28465 WSAECONNRESET failure on sync causes build to be marked as failed Change By: Brian Collum Status: Open Closed Resolution: NotADefect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-28465) WSAECONNRESET failure on sync causes build to be marked as failed
Title: Message Title Brian Collum created an issue Jenkins / JENKINS-28465 WSAECONNRESET failure on sync causes build to be marked as failed Issue Type: Bug Assignee: Rob Petti Components: perforce-plugin Created: 18/May/15 9:05 PM Environment: Windows 7 64-bit, Jenkins 1.613, Perforce Plugin 1.3.34, P4V 2014.2/951414, P4 2014.2/943801 Labels: plugin Priority: Minor Reporter: Brian Collum Occasionally our project reports build failures, but when we go to look at the build output it appears that the only thing that failed was the p4 sync command. Upon running the build manually again it works fine. Here is the dump that all of the failures look like: [none] $ C:\Program Files\Perforce\p4 -s sync -f //automated_build_sepac_main/...@204714 Caught exception communicating with perforce. Errors encountered while force syncing: error: RpcTransport: partial message read error: TCP receive failed. error: read: socket: WSAECONNRESET com.tek42.perforce.PerforceException: Errors
[JIRA] [perforce-plugin] (JENKINS-28465) WSAECONNRESET failure on sync causes build to be marked as failed
Title: Message Title Brian Collum edited a comment on JENKINS-28465 Re: WSAECONNRESET failure on sync causes build to be marked as failed IguessIwouldexpectittopossiblyretrytheconnectionagain?OrmarkthepossiblymarkthebuildasABORTEDorsomethingsimilar(thoughIseewhyfromyourstandpointyoumaynotwanttodothat).Eitherway,thanksforthehelp.Wehavebeensearchingforthesourceoftheproblembutnoneofourdevelopershaveseenaissue.OnlyourJenkinsinstancegetserrorslikethis. ButthatcouldjustbebecauseJenkinshaslotmoretrafficgoingthroughit. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-28465) WSAECONNRESET failure on sync causes build to be marked as failed
Title: Message Title Brian Collum commented on JENKINS-28465 Re: WSAECONNRESET failure on sync causes build to be marked as failed Alright, well thanks for the feedback. I'll go ahead and close this. This will be a fun call with our IT Department... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
