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

Chris Withers created JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

Issue Type:	Bug
Affects Versions:	current
Assignee:	Unassigned
Components:	subversion
Created:	24/Jul/12 11:04 AM
Description:	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.
Environment:	sles 11, Jenkins 1.470, subversion server is CollabNet Subversion Edge 1.3.1
Project:	Jenkins
Priority:	Major
Reporter:	Chris Withers

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

 

Chris Withers updated JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

nealeu commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

SCM/JIRA link daemon commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Alexandre Colucci commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Chris Simmons commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Chris Simmons commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Yury Pukhalsky commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Chris Withers commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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 message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

David Humeniuk commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

john broome commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Bartosy Tworek commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

SCM/JIRA link daemon commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Ben Hines commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

maik s commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Andreas W commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Andreas W commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Bernhard Hiller commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Peter Thorson commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Nicola Tarbet commented on JENKINS-14550

"Checksum mismatch while updating" with Subversion Plugin 1.42

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.