-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
Component/s: mercurial-plugin
-
Environment:1.392 server, 1.35 plugin, Linux, some old Hg
Sometimes a job using caching Hg seems to hang in the initial pull stage, for hours or days, but recovers and continues when killed:
Started by timer Building remotely on Some-Node [61D69DEDAA484957122A96D78FE5E04372216A47-repo-name] $ hg pull killed! ERROR: Failed to use repository cache for http://.../repo-name/ java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) at hudson.Proc$LocalProc.join(Proc.java:226) at hudson.Launcher$ProcStarter.join(Launcher.java:280) at hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:298) at hudson.plugins.mercurial.Cache.repositoryCache(Cache.java:97) at hudson.plugins.mercurial.MercurialSCM.cachedSource(MercurialSCM.java:650) at hudson.plugins.mercurial.MercurialSCM.update(MercurialSCM.java:478) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:419) at hudson.model.AbstractProject.checkout(AbstractProject.java:1118) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:480) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:412) at hudson.model.Run.run(Run.java:1362) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) [job-name] $ hg incoming ...
Configuring the build timeout plugin has no effect, I suppose because build wrappers are initialized only after the SCM update is invoked. There should therefore be some kind of automatic timeout on pulls, just as there is already on polls.
