[JIRA] [core] (JENKINS-19741) Massive jobs execution causes issues in lastSuccessfulBuild permalink update

36 views
Skip to first unread message

smr@sumost.ca (JIRA)

unread,
Mar 7, 2016, 11:16:03 AM3/7/16
to jenkinsc...@googlegroups.com
Steve Robbins commented on Bug JENKINS-19741
 
Re: Massive jobs execution causes issues in lastSuccessfulBuild permalink update

I don't think this has anything to do with parallel jobs execution ... except perhaps that it is easier to expose the race condition?

We see the same failures to update permalinks – both lastSuccessfulBuild and lastFailedBuild – on a small installation without parallel jobs (one node, with #executors set to 1) and with low execution rates. Also the server is Windows Server 2012 R2 Standard, so not a linux-only issue. Jenkins ver. 1.642.2.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

smr@sumost.ca (JIRA)

unread,
Mar 7, 2016, 11:18:02 AM3/7/16
to jenkinsc...@googlegroups.com
Steve Robbins edited a comment on Bug JENKINS-19741
I don't think this has anything to do with parallel jobs execution ... except perhaps that it is easier to expose the race condition?

We see the same failures to update permalinks -- both lastSuccessfulBuild and lastFailedBuild -- on a small installation without parallel jobs (one node, with #executors set to 1) and with low execution rates.  Also the server is Windows Server 2012 R2 Standard, so not a linux-only issue.  Jenkins ver. 1.642.2.

Another difference is that instead of NoSuchFile, we see DirectoryNotEmptyException:

Mar 05, 2016 4:06:09 AM jenkins.model.PeepholePermalink updateCache
WARNING: Failed to update hudson.model.FreeStyleProject@320509[40018_mmiDotNetMath_main] lastSuccessfulBuild permalink for 40018_mmiDotNetMath_main #767
java.nio.file.DirectoryNotEmptyException: C:\Jenkins\jobs\40018_mmiDotNetMath_main\builds\lastSuccessfulBuild
at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source)
at java.nio.file.Files.delete(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at hudson.Util.deleteFile(Util.java:255)
at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:113)
at jenkins.model.PeepholePermalink.writeSymlink(PeepholePermalink.java:200)
at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:150)
at jenkins.model.PeepholePermalink$RunListenerImpl.onCompleted(PeepholePermalink.java:237)
at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:201)
at hudson.model.Run.execute(Run.java:1783)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)

israodin@gmail.com (JIRA)

unread,
Nov 3, 2016, 5:15:05 AM11/3/16
to jenkinsc...@googlegroups.com

Hi all
We Have some problem with lasBuild on Jenkins ver. 1.651.3

WARNING: Failed to update hudson.model.FreeStyleProject@1c6fcad[CD-CFW_Selenium_Part1] lastSuccessfulBuild permalink for CD-CFW_Selenium_Part1 #5631
java.nio.file.DirectoryNotEmptyException: c:\Jenkins\jobs\CD-CFW_Selenium_Part1\builds\lastSuccessfulBuild


at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source)
at java.nio.file.Files.delete(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)

at hudson.Util.deleteFile(Util.java:257)


at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:113)
at jenkins.model.PeepholePermalink.writeSymlink(PeepholePermalink.java:200)
at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:150)

at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:122)
at hudson.model.Job.getLastSuccessfulBuild(Job.java:913)
at jenkins.tasks.SimpleBuildStep$LastBuildActionFactory.createFor(SimpleBuildStep.java:113)
at jenkins.tasks.SimpleBuildStep$LastBuildActionFactory.createFor(SimpleBuildStep.java:99)
at hudson.model.Actionable.createFor(Actionable.java:107)
at hudson.model.Actionable.getAllActions(Actionable.java:98)
at hudson.model.Actionable.getAction(Actionable.java:165)
at hudson.plugins.nunit.NUnitPublisher.getProjectAction(NUnitPublisher.java:94)
at hudson.tasks.BuildStepCompatibilityLayer.getProjectActions(BuildStepCompatibilityLayer.java:98)
at hudson.model.Project.createTransientActions(Project.java:252)
at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755)
at hudson.model.AbstractProject.onLoad(AbstractProject.java:339)
at hudson.model.Project.onLoad(Project.java:98)
at hudson.model.Items.load(Items.java:327)
at jenkins.model.Jenkins$18.run(Jenkins.java:2720)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$8.runTask(Jenkins.java:926)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

uinetov@gmail.com (JIRA)

unread,
Nov 27, 2018, 10:57:03 AM11/27/18
to jenkinsc...@googlegroups.com

my case

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

uinetov@gmail.com (JIRA)

unread,
Nov 27, 2018, 11:00:02 AM11/27/18
to jenkinsc...@googlegroups.com
Yuriy Inetov edited a comment on Bug JENKINS-19741
my My case : JENKINS-54863

I do not understand how much they are the same..

o.v.nenashev@gmail.com (JIRA)

unread,
Dec 6, 2018, 3:41:02 AM12/6/18
to jenkinsc...@googlegroups.com

Yuriy Inetov The error messages are not 100% same, because the AtomicFile logic has changed significantly since 2013. But yes, the rootcause is the same

Reply all
Reply to author
Forward
0 new messages