Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • sles 11, Jenkins 1.470, subversion server is CollabNet Subversion Edge 1.3.1

      After upgrading to 1.42 of the plugin, using the "Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'" svn strategy intermittently results in errors that look like the following:

      ERROR: Failed to update svn://<path>
      org.tmatesoft.svn.core.SVNException: svn: E155017: Checksum mismatch while updating '/opt/jenkins/jobs/<job>/workspace/<path to folder>/.svn/text-base/<filename>.svn-base'; expected: '151afc3b6d79443cc57fd52080d5f4d7', actual: '97acf6bf0db0d86168866633488b1a93'
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:85)
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:69)
      at org.tmatesoft.svn.core.internal.io.svn.SVNEditModeReader.driveEditor(SVNEditModeReader.java:250)
      at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.update(SVNRepositoryImpl.java:1503)
      at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:557)
      at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414)
      at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:324)
      at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27)
      at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11)
      at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
      at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
      at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391)
      at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136)
      at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
      at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
      at hudson.FilePath.act(FilePath.java:842)
      at hudson.FilePath.act(FilePath.java:824)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1242)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
      at hudson.model.Run.execute(Run.java:1460)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:239)

      I clicked the "Downgrade to 1.39" button in the installed plugins section, restarted Jenkins and the problem appears to be solved.

      However, I notice the installed plugins section now says I have 1.34 installed, which is a little confusing.

          [JENKINS-14550] "Checksum mismatch while updating" with Subversion Plugin 1.42

          Chris Withers added a comment -

          Forgot to say, to make matters worse, when the checksum problem occurs, the Subversion Plugin doesn't fail the build, causing spurious failures in build steps later in the job.

          Chris Withers added a comment - Forgot to say, to make matters worse, when the checksum problem occurs, the Subversion Plugin doesn't fail the build, causing spurious failures in build steps later in the job.

          nealeu added a comment -

          I also get this issue with "use svn update as much as possible".

          This is a notable issue as if this happens overnight, we get builds repeated every time SVN is polled, so in our case the build server was flat out all night.

          If there is a genuine error, then I'd suggest that the plugin should fallback to doing a clean checkout anyway.

          nealeu added a comment - I also get this issue with "use svn update as much as possible". This is a notable issue as if this happens overnight, we get builds repeated every time SVN is polled, so in our case the build server was flat out all night. If there is a genuine error, then I'd suggest that the plugin should fallback to doing a clean checkout anyway.

          Code changed in jenkins
          User: Nicolas De Loof
          Path:
          src/main/java/hudson/scm/subversion/UpdateUpdater.java
          http://jenkins-ci.org/commit/subversion-plugin/a7d6b393b785bb44328302e8778d85fd7c278052
          Log:
          JENKINS-14550 switch to checkoutUpdater on corrupted workspace detection

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/scm/subversion/UpdateUpdater.java http://jenkins-ci.org/commit/subversion-plugin/a7d6b393b785bb44328302e8778d85fd7c278052 Log: JENKINS-14550 switch to checkoutUpdater on corrupted workspace detection

          I upgraded yesterday the Subversion Plugin to 1.42 and I also get the same 'Checksum mismatch' error. Reverting to 1.39 fixes the issue.

          Alexandre Colucci added a comment - I upgraded yesterday the Subversion Plugin to 1.42 and I also get the same 'Checksum mismatch' error. Reverting to 1.39 fixes the issue.

          Chris Simmons added a comment -

          Confirmed the same behavior with v1.42. I'm attempting to downgrade to v1.41. It might be coincidence, but this only appears to happen to projects where we have renamed or removed files in SVN.

          UPDATE: v1.41 appears to have the same issue. Going to further downgrade.

          Chris Simmons added a comment - Confirmed the same behavior with v1.42. I'm attempting to downgrade to v1.41. It might be coincidence, but this only appears to happen to projects where we have renamed or removed files in SVN. UPDATE: v1.41 appears to have the same issue. Going to further downgrade.

          Chris Simmons added a comment -

          I can confirm that v1.39 appears to be the latest build that works.

          Chris Simmons added a comment - I can confirm that v1.39 appears to be the latest build that works.

          This seems to be very similar to a much older issue.

          David Humeniuk added a comment - This seems to be very similar to a much older issue.

          To add to Chris Simmons' observation.

          I think it's indeed connected with renaming files. I've seen (and see) it only if the files are renamed in SVN.

          Yury Pukhalsky added a comment - To add to Chris Simmons' observation. I think it's indeed connected with renaming files. I've seen (and see) it only if the files are renamed in SVN.

          Chris Withers added a comment -

          The specific case we had was when the plugin performed an svn update on trunk that involved a revision where a file was added on a branch and then that branch was merged into trunk.

          Annoyingly, we had this re-occur recently, even though we're now on what purports to be 1.34.
          Anyone know how we could upgrade to 1.39?

          Chris Withers added a comment - The specific case we had was when the plugin performed an svn update on trunk that involved a revision where a file was added on a branch and then that branch was merged into trunk. Annoyingly, we had this re-occur recently, even though we're now on what purports to be 1.34. Anyone know how we could upgrade to 1.39?

          This issue is included in the changelog for 1.43, but this issue hasn't been updated to reflect

          David Humeniuk added a comment - This issue is included in the changelog for 1.43, but this issue hasn't been updated to reflect

          john broome added a comment -

          I'm experiencing this issue with version 1.43 of the subversion plugin on Jenkins 1.466.2:

          svn: E155017: Checksum mismatch while updating '/opt/hudson/data/jobs/<job>/workspace/test/cucumber/.svn/text-base/job.feature.svn-base'; expected: '1e29e62bb3d127678d36ea0d24594bc9', actual: '0bb53e0a9560a2dc6abd225e2771297d'
          at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
          at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
          at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:675)
          at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)

          john broome added a comment - I'm experiencing this issue with version 1.43 of the subversion plugin on Jenkins 1.466.2: svn: E155017: Checksum mismatch while updating '/opt/hudson/data/jobs/<job>/workspace/test/cucumber/.svn/text-base/job.feature.svn-base'; expected: '1e29e62bb3d127678d36ea0d24594bc9', actual: '0bb53e0a9560a2dc6abd225e2771297d' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:675) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)

          I've experienced same issue... lot of "Checksum mismatch while updating".
          Downgrading to subversion plugin ver 1.39 fixed that issue.
          Using Jenkins ver. 1.491

          Bartosy Tworek added a comment - I've experienced same issue... lot of "Checksum mismatch while updating". Downgrading to subversion plugin ver 1.39 fixed that issue. Using Jenkins ver. 1.491

          Code changed in jenkins
          User: Nicolas De Loof
          Path:
          src/main/java/hudson/scm/subversion/UpdateUpdater.java
          http://jenkins-ci.org/commit/subversion-plugin/638f83527e8244aa086c5c2f571960c964f9acd5
          Log:
          JENKINS-14550 SVNException E155017 may be wrapped into a E175002
          so lookup the root cause

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/scm/subversion/UpdateUpdater.java http://jenkins-ci.org/commit/subversion-plugin/638f83527e8244aa086c5c2f571960c964f9acd5 Log: JENKINS-14550 SVNException E155017 may be wrapped into a E175002 so lookup the root cause

          Ben Hines added a comment -

          this still occurs with 1.44 /jenkins 1.498 btw. Very frustrating

          Ben Hines added a comment - this still occurs with 1.44 /jenkins 1.498 btw. Very frustrating

          maik s added a comment -

          After switching Subversion URL from http:// to svn:// Jenkins checks out a fresh workspace after checksum mismatch.

          maik s added a comment - After switching Subversion URL from http:// to svn:// Jenkins checks out a fresh workspace after checksum mismatch.

          Andreas W added a comment -

          Happens here as well, it makes Jenkins unuable for us, so it should be a blocker.

          Using SVN plugin 1.44 and jenkins 1.498.

          Andreas W added a comment - Happens here as well, it makes Jenkins unuable for us, so it should be a blocker. Using SVN plugin 1.44 and jenkins 1.498.

          Andreas W added a comment -

          I wanted to add this is definitly not a problem caused by a crash or forced shutdown, as it happened on different computers (jenkins master and jenkins slave) and in different jobs with seperate checkout. The error occured on the same file. On the other side no developers who used a normal svn client reported a similar failure during checkout, so it is not a problem of the svn server.

          Andreas W added a comment - I wanted to add this is definitly not a problem caused by a crash or forced shutdown , as it happened on different computers (jenkins master and jenkins slave) and in different jobs with seperate checkout. The error occured on the same file. On the other side no developers who used a normal svn client reported a similar failure during checkout, so it is not a problem of the svn server .

          Do a manual update of the source with Tortoise - that's a feasable workaround for such cases.
          But meanwhile, the email inbox can be spammed with many error messages from failed builds, which were caused by Jenkin's failure to update sources.

          Bernhard Hiller added a comment - Do a manual update of the source with Tortoise - that's a feasable workaround for such cases. But meanwhile, the email inbox can be spammed with many error messages from failed builds, which were caused by Jenkin's failure to update sources.

          Peter Thorson added a comment -

          In searching this issue, I noticed a similar issue on the JetBrains site which they say is fixed with svnkit 1.7.5-v1. See here: http://youtrack.jetbrains.com/issue/IDEA-83673#comment=27-379397

          Based on the GIT site, https://github.com/jenkinsci/svnkit, I believe the 1.7.6 version of svnkit has been merged in October (and 1.7.5-v1 in July).

          In my Jenkins pluginManager I only see Subversion Plugin 1.45 offered. (I am at 1.44.) Based on https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin, it looks like 1.45 includes SVNKit 1.7.6 since January. Hopefully this new version will prevent these errors from happening anymore.

          Peter Thorson added a comment - In searching this issue, I noticed a similar issue on the JetBrains site which they say is fixed with svnkit 1.7.5-v1. See here: http://youtrack.jetbrains.com/issue/IDEA-83673#comment=27-379397 Based on the GIT site, https://github.com/jenkinsci/svnkit , I believe the 1.7.6 version of svnkit has been merged in October (and 1.7.5-v1 in July). In my Jenkins pluginManager I only see Subversion Plugin 1.45 offered. (I am at 1.44.) Based on https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin , it looks like 1.45 includes SVNKit 1.7.6 since January. Hopefully this new version will prevent these errors from happening anymore.

          Nicola Tarbet added a comment -

          We can reliably reproduce the issue by renaming and then modifying the file.
          On Jenkins ver. 1.514, Subversion plugin 1.45, svnkit 1.7.6
          check out strategy: Use 'svn update' as much as possible

          We had to downgrade to Subversion plugin 1.39.
          For those wondering how to get their downgrade to stick you need to "pin" the downgraded plugin
          https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins

          Nicola Tarbet added a comment - We can reliably reproduce the issue by renaming and then modifying the file. On Jenkins ver. 1.514, Subversion plugin 1.45, svnkit 1.7.6 check out strategy: Use 'svn update' as much as possible We had to downgrade to Subversion plugin 1.39. For those wondering how to get their downgrade to stick you need to "pin" the downgraded plugin https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins

          Ryan Kalinowski added a comment - - edited

          Currently experiencing this on 1.42. Trying to decide whether to downgrade to 1.39 or to try upgrading 1.53. Can anyone comment on whether this is resolved in 1.53?

          UPDATE
          Upgraded Jenkins from 1.529 to 1.535 and changed the project from using svn update to using a clean copy, and it looks like it's working now. Still on 1.42 of the svn plugin.

          Ryan Kalinowski added a comment - - edited Currently experiencing this on 1.42. Trying to decide whether to downgrade to 1.39 or to try upgrading 1.53. Can anyone comment on whether this is resolved in 1.53? UPDATE Upgraded Jenkins from 1.529 to 1.535 and changed the project from using svn update to using a clean copy, and it looks like it's working now. Still on 1.42 of the svn plugin.

          Bernd bep added a comment -

          I do not experience this with SVN Plugin 1.50. (I did with older versions). Be careful with 1.51/1.53: https://issues.jenkins-ci.org/browse/JENKINS-19600

          Bernd bep added a comment - I do not experience this with SVN Plugin 1.50. (I did with older versions). Be careful with 1.51/1.53: https://issues.jenkins-ci.org/browse/JENKINS-19600

          Oleg Nenashev added a comment -

          Does anyone see the issue on Subversion 2.0+?

          Oleg Nenashev added a comment - Does anyone see the issue on Subversion 2.0+?

            Unassigned Unassigned
            cjw296 Chris Withers
            Votes:
            27 Vote for this issue
            Watchers:
            34 Start watching this issue

              Created:
              Updated: