[
https://issues.apache.org/jira/browse/BUILDS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113103#comment-14113103
]
Konstantin Kolinko commented on BUILDS-9:
-----------------------------------------
log4j2 project configures "SVN" step as addStep(SVN(repourl=...)) without any
values for mode or method. It means that those have default values
mode="incremental", method=None. \[1]
In this configuration Buildbot does the following
(in methods incremental(), _sourcedirIsUpdatable() in \[2] ):
1. Checks that ".svn" directory is present
2. Calls "svn info --xml" and parses its stdout as XML.
3. Verifies that repository URL returned by Step 2 is as expected.
4. If repository URL is OK then it performs "svn update".
In this case the step 2 fails.
My guess is that svn working copy is in an older format and needs an "svn
upgrade" call on it.
\[1] http://docs.buildbot.net/current/manual/cfg-buildsteps.html#step-SVN
\[2]
https://github.com/buildbot/buildbot/blob/master/master/buildbot/steps/source/svn.py#L258
> Some Buildbot Builds failing due to corupted xml in svn step
> ------------------------------------------------------------
>
> Key: BUILDS-9
> URL: https://issues.apache.org/jira/browse/BUILDS-9
> Project: Infra Build Platform
> Issue Type: Bug
> Components: Buildbot
> Environment: Currently only seems to happen on lares_ubuntu which as
> svn 1.8.8
> Reporter: Gavin
> Assignee: Gavin
>
> most builds fail during the svn checkout|update step with the error message
> 'Corrupted xml, aborting step'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
