[JIRA] (JENKINS-27263) Checkout of svn:externals fails silently and intermittently

184 views
Skip to first unread message

jenkins@mockies.de (JIRA)

unread,
Aug 4, 2018, 10:27:08 AM8/4/18
to jenkinsc...@googlegroups.com
Christoph Vogtländer commented on Bug JENKINS-27263
 
Re: Checkout of svn:externals fails silently and intermittently

I'm experiencing the same issue with Subversion plugin version 2.10.5 and 2.11.1. During checkout/update of externals the process simply proceeds with the next external item. No "At revision <rev>" message shown.

I don't experience a delay between the last checked out file and the next "<-- Got one external: ... " message.

Both, Windows and Linux nodes are affected.

Also, I don't believe this is a server or connection problem. The build server and the subversion server are on a local network. There have never been any network related problems. Using Jenkins, this is suddenly happening quite regularly. Using the command line client to update the working copy manually works without any problems. And this sort of problem has never occurred to any team member (using either TortoiseSVN client under Windows or SmartSVN or command line client under Linux). The server is a VisualSVN 3.6.3 (Subversion 1.9.5, Apache 2.2.34) on Windows Server 2012.

There are no errors in the Jenkins log. But, there are errors in the Subversion Server log:

Log Name: VisualSVNServer
Source: VisualSVN Server 3.6
Date: 8/4/2018 3:31:44 PM
Event ID: 1001
Task Category: Apache
Level: Error
Keywords: Classic
User: >user<
Computer: >server<
Description:
Unknown error [500, #106]
[client xxx.xxx.xxx.xxx]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="VisualSVN Server 3.6" />
 <EventID Qualifiers="0">1001</EventID>
 <Level>2</Level>
 <Task>2</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2018-08-04T13:31:44.000000000Z" />
 <EventRecordID>55045</EventRecordID>
 <Channel>VisualSVNServer</Channel>
 <Computer>>server<</Computer>
 <Security UserID=">userid<" />
 </System>
 <EventData>
 <Data>Unknown error [500, #106]
</Data>
 <Data>xxx.xxx.xxx.xxx</Data>
 </EventData>
</Event>

Log Name: VisualSVNServer
Source: VisualSVN Server 3.6
Date: 8/4/2018 3:31:44 PM
Event ID: 1001
Task Category: Apache
Level: Error
Keywords: Classic
User: >user<
Computer: >server<
Description:
A failure occurred while driving the update report editor [500, #106]
[client xxx.xxx.xxx.xxx]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="VisualSVN Server 3.6" />
 <EventID Qualifiers="0">1001</EventID>
 <Level>2</Level>
 <Task>2</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2018-08-04T13:31:44.000000000Z" />
 <EventRecordID>55044</EventRecordID>
 <Channel>VisualSVNServer</Channel>
 <Computer>>server<</Computer>
 <Security UserID=">userid<" />
 </System>
 <EventData>
 <Data>A failure occurred while driving the update report editor [500, #106]
</Data>
 <Data>xxx.xxx.xxx.xxx</Data>
 </EventData>
</Event>

Log Name: VisualSVNServer
Source: VisualSVN Server 3.6
Date: 8/4/2018 3:31:44 PM
Event ID: 1001
Task Category: Apache
Level: Error
Keywords: Classic
User: >user<
Computer: >server<
Description:
Provider encountered an error while streaming a REPORT response. [500, #0]
[client xxx.xxx.xxx.xxx]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="VisualSVN Server 3.6" />
 <EventID Qualifiers="0">1001</EventID>
 <Level>2</Level>
 <Task>2</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2018-08-04T13:31:44.000000000Z" />
 <EventRecordID>55043</EventRecordID>
 <Channel>VisualSVNServer</Channel>
 <Computer>>server<</Computer>
 <Security UserID=">userid<" />
 </System>
 <EventData>
 <Data>Provider encountered an error while streaming a REPORT response. [500, #0]
</Data>
 <Data>xxx.xxx.xxx.xxx</Data>
 </EventData>
</Event>

I'm not sure whether these errors are related to this issue or not. The errors occur during the check out of the external. But there are many more files checked out until the issue occurs and the next external gets processed (the last checked out file for the external has time stamp 16:07:35). As there are several parallel check outs running at that time the server errors might not be related. A quick web search shows that the errors might be related to client-side timeouts.

 

 

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

jenkins@mockies.de (JIRA)

unread,
Aug 9, 2018, 10:23:03 AM8/9/18
to jenkinsc...@googlegroups.com

Setting "cancelProcessOnExternalsFail: true" (checkout step) will fail the build. This is an example stack trace:

[Checkout branch2] ERROR: Failed to update https://server/repo
[Checkout branch2] org.tmatesoft.svn.core.SVNException: svn: E205011: Failed processing one or more externals definitions: <Qt>
[Checkout branch2] 	at hudson.scm.subversion.SubversionUpdateEventHandler.handleEvent(SubversionUpdateEventHandler.java:145)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.handleEvent(SvnOperationRunner.java:67)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.handleEvent(SvnOperationRunner.java:72)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternalsChange(SvnNgAbstractUpdate.java:383)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternals(SvnNgAbstractUpdate.java:315)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:279)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:115)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:40)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
[Checkout branch2] 	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
[Checkout branch2] 	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239)
[Checkout branch2] 	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
[Checkout branch2] 	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
[Checkout branch2] 	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
[Checkout branch2] 	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
[Checkout branch2] 	at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:161)
[Checkout branch2] 	at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:168)
[Checkout branch2] 	at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1041)
[Checkout branch2] 	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1017)
[Checkout branch2] 	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:990)
[Checkout branch2] 	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2913)
[Checkout branch2] 	at hudson.remoting.UserRequest.perform(UserRequest.java:212)
[Checkout branch2] 	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
[Checkout branch2] 	at hudson.remoting.Request$2.run(Request.java:369)
[Checkout branch2] 	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
[Checkout branch2] 	at java.util.concurrent.FutureTask.run(Unknown Source)
[Checkout branch2] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[Checkout branch2] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[Checkout branch2] 	at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
[Checkout branch2] 	at java.lang.Thread.run(Unknown Source)
[Checkout branch2] ERROR: Subversion update failed

So at least such an error won't get through unnoticed.

Reply all
Reply to author
Forward
0 new messages