[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title John Lengeling commented on JENKINS-52842 Re: xUnit plugin blocks PingThread responses Other than the 1 hung job soon after I loaded xunit-2.3.8-rc831.cbb77af6dfed, the issue looks to be improved. The test job has been running hourly for the past 2 days with 0 hangs versus several hangs per day with 2.3.7. So you might be on the right track. I did also increase the ping thread interval and timeout values to 1500/1200, but I have now restored the ping thread interval/timeout values back to the defaults (300/240). I will let that bake for a few days. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192770.1533150138000.8459.1581549060178%40Atlassian.JIRA.
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title John Lengeling commented on JENKINS-52842 Re: xUnit plugin blocks PingThread responses Nickolas, I had 7 successful builds before the pingThread killed the node during xunit processing when running xunit version 2.3.8-rc831.cbb77af6dfed. Console Output:Console Output: [2020-02-10T13:35:50.172Z] WARNING: XUnitBuilder step is deprecated since 2.x, it has been replaced by XUnitPublisher. This builer will be remove in version 3.x [2020-02-10T13:35:50.175Z] INFO: Starting to record. [2020-02-10T13:35:50.175Z] INFO: Processing GoogleTest-1.8[2020-02-10T13:35:50.250Z] INFO: [GoogleTest-1.8] - 959 test report file(s) were found with the pattern 'j/wr/build/_TestArtifacts*/*.xml' relative to '/home/jenkins/workspace/kb/os' for the testing framework 'GoogleTest-1.8'. Theads related to this aws node i-0b11d0f08d8d59c51: dev-large (i-0b11d0f08d8d59c51) "org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#93] / waiting for EC2 (foo-aws) - dev-large (i-0b11d0f08d8d59c51) id=166000" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) hudson.FilePath.act(FilePath.java:1069) hudson.FilePath.act(FilePath.java:1058) org.jenkinsci.plugins.xunit.XUnitProcessor.processTestsReport(XUnitProcessor.java:195) org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:159) org.jenkinsci.plugins.xunit.XUnitBuilder.perform(XUnitBuilder.java:126) org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$339/847132060.run(Unknown Source) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) "Channel reader thread: EC2 (foo-aws) - dev-large (i-0b11d0f08d8d59c51)" daemon prio=5 WAITING java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:502) com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212) com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127) com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:933) com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:91) hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title John Lengeling commented on JENKINS-52842 Re: xUnit plugin blocks PingThread responses Will test the plugin version that you provided. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192770.1533150138000.5151.1581310260171%40Atlassian.JIRA.
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title
John Lengeling commented on JENKINS-52842
Re: xUnit plugin blocks PingThread responses
Sorry I sent you the stacktrace from the job console which is after the job is aborted. fooTool.groovy is our Jenkins pipeline library which calls has a publishUnitTests method which calls XUnitBuilder. {{ try { steps.step([$class : 'XUnitBuilder', testTimeMargin: '3000', thresholdMode: 2, thresholds: [ [ $class : 'FailedThreshold', failureNewThreshold : '100', failureThreshold : '100', unstableNewThreshold: '100', unstableThreshold : '100' ], [ $class : 'SkippedThreshold', failureNewThreshold : '100', failureThreshold : '100', unstableNewThreshold: '100', unstableThreshold : '100' ] ], tools : [ [ $class : 'GoogleTestType', deleteOutputFiles : true, failIfNotNew : false, pattern : filePattern, skipNoTestFiles : true, stopProcessingIfError: true ] ] ]) }} Here is the thread dump of the thread that is hanging in xunit: {{ "org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution 2624 / waiting for EC2 (foo-aws) - team-bar-large (i-086328a69a4a0b130) id=8001805" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) hudson.FilePath.act(FilePath.java:1069) hudson.FilePath.act(FilePath.java:1058) org.jenkinsci.plugins.xunit.XUnitProcessor.processTestsReport(XUnitProcessor.java:195) org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:159) org.jenkinsci.plugins.xunit.XUnitBuilder.perform(XUnitBuilder.java:126) org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) }}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60914) Freestyle job with urltrigger doesn't inject parameter with default value
Title: Message Title
John Lengeling updated an issue
Jenkins / JENKINS-60914
Freestyle job with urltrigger doesn't inject parameter with default value
Change By:
John Lengeling
We just upgraded from Jenkins 2.176.3 -> 2.204.1 and also updated to latest plugin versions.We have a freestyle job that quit working after the upgrade that uses the urltrigger plugin. The freestyle job has a simple string parameter and its value should be injected into the job as an environment variable.Running urltrigger 0.47, the string parameter is not getting injected when the urltrigger fires the job. This was working using urltrigger 0. 43 45 . We downgraded to 0. 43 45 and this job started working again.The URLTrigger log from 0.47 when failing: {noformat} Polling started on Jan 29, 2020 10:43:04 AM Polling for the job testfoo Looking nodes where the poll can be run. Looking for a candidate node to run the poll. Trying to find an eligible node with the assigned project label coord. Polling remotely on jenkinsserver *Resolving environment variables using global values* Using Basic Authentication with the user 'build' Invoking the url: [https://jenkinsserver.foo.com/job/test/job/test/job/testing/lastSuccessfulBuild/buildNumber/] [https://gen4cc-os.virtd.deere.com/job/gen4cc-os/job/gen4os/job/release-20-1/lastSuccessfulBuild/buildNumber/] Inspecting the content The content of the URL has changed. The content has changed. Polling complete. Took 0.61 sec. Changes found. Scheduling a build. {noformat} When running with the working 0. 43 45 plugin, the urltrigger log shows slightly different behavior. It logs "Resolving environment variables using last build values" instead of when it is failing as above "Resolving environment variables using global values" Looks like recent changes with the code emitting the message commented out:[https://github.com/jenkinsci/urltrigger-plugin/blob/63b65488e3cf89d1c40840fe881d5b2b59233ed7/src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java#L229] As a workaround, we downgraded to 0. 43 45 for now.
Add Comment
[JIRA] (JENKINS-60914) Freestyle job with urltrigger doesn't inject parameter with default value
Title: Message Title
John Lengeling updated an issue
Jenkins / JENKINS-60914
Freestyle job with urltrigger doesn't inject parameter with default value
Change By:
John Lengeling
We just upgraded from Jenkins 2.176.3 -> 2.204.1 and also updated to latest plugin versions.We have a freestyle job that quit working after the upgrade that uses the urltrigger plugin. The freestyle job has a simple string parameter and its value should be injected into the job as an environment variable.Running urltrigger 0.47, the string parameter is not getting injected when the urltrigger fires the job. This was working using urltrigger 0.43. We downgraded to 0.43 and this job started working again.The URLTrigger log from 0.47 when failing: {noformat} Polling started on Jan 29, 2020 10:43:04 AM Polling for the job testfoo Looking nodes where the poll can be run. Looking for a candidate node to run the poll. Trying to find an eligible node with the assigned project label coord. Polling remotely on jenkinsserver *Resolving environment variables using global values* Using Basic Authentication with the user 'build' Invoking the url: [https://jenkinsserver.foo.com/job/test/job/test/job/testing/lastSuccessfulBuild/buildNumber/] [https://gen4cc-os.virtd.deere.com/job/gen4cc-os/job/gen4os/job/release-20-1/lastSuccessfulBuild/buildNumber/] Inspecting the content The content of the URL has changed. The content has changed. Polling complete. Took 0.61 sec. Changes found. Scheduling a build. {noformat} When running with the working 0.43 plugin, the urltrigger log shows slightly different behavior. It logs "Resolving environment variables using last build values" instead of when it is failing as above "Resolving environment variables using global values" Looks like recent changes with the code emitting the message commented out:[https://github.com/jenkinsci/urltrigger-plugin/blob/63b65488e3cf89d1c40840fe881d5b2b59233ed7/src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java#L229] As a workaround, we downgraded to 0.43 for now.
Add Comment
[JIRA] (JENKINS-60914) Freestyle job with urltrigger doesn't inject parameter with default value
Title: Message Title
John Lengeling updated an issue
Jenkins / JENKINS-60914
Freestyle job with urltrigger doesn't inject parameter with default value
Change By:
John Lengeling
We just upgraded from Jenkins 2.176.3 -> 2.204.1 and also updated to latest plugin versions.We have a freestyle job that quit working after the upgrade that uses the urltrigger plugin. The freestyle job has a simple string parameter and its value should be injected into the job as an environment variable.Running urltrigger 0.47, the string parameter is not getting injected when the urltrigger fires the job. This was working using urltrigger 0.43. We downgraded to 0.43 and this job started working again.The URLTrigger log from 0.47 when failing: {{ Polling started on Jan 29, 2020 10:43:04 AM }} {{ Polling for the job testfoo }} {{ Looking nodes where the poll can be run. }}{{ Looking for a candidate node to run the poll. }}{{ Trying to find an eligible node with the assigned project label coord. }} {{ Polling remotely on jenkinsserver }}{{ *Resolving environment variables using global values* }} {{ Using Basic Authentication with the user 'build' }}{{ Invoking the url: }}{{ [https://jenkinsserver.foo.com/job/test/job/test/job/testing/lastSuccessfulBuild/buildNumber/ ] | [ https://gen4cc-os.virtd.deere.com/job/gen4cc-os/job/gen4os/job/release-20-1/lastSuccessfulBuild/buildNumber/] }}{{}}{{ Inspecting the content The content of the URL has changed. }} {{ The content has changed. }} {{ Polling complete. }} {{ Took 0.61 sec. }} {{ Changes found. }}{{ Scheduling a build. }} When running with the working 0.43 plugin, the urltrigger log shows slightly different behavior. It logs "Resolving environment variables using last build values" instead of when it is failing as above "Resolving environment variables using global values" Looks like recent changes with the code emitting the message commented out:[https://github.com/jenkinsci/urltrigger-plugin/blob/63b65488e3cf89d1c40840fe881d5b2b59233ed7/src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java#L229] As a workaround, we downgraded to 0.43 for now.
Add Comment
[JIRA] (JENKINS-60914) Freestyle job with urltrigger doesn't inject parameter with default value
Title: Message Title
John Lengeling created an issue
Jenkins / JENKINS-60914
Freestyle job with urltrigger doesn't inject parameter with default value
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
urltrigger-plugin
Created:
2020-01-29 23:06
Environment:
Jenkins 2.204.1, urltrigger 0.47, Ubuntu 14.04
Priority:
Minor
Reporter:
John Lengeling
We just upgraded from Jenkins 2.176.3 -> 2.204.1 and also updated to latest plugin versions. We have a freestyle job that quit working after the upgrade that uses the urltrigger plugin. The freestyle job has a simple string parameter and its value should be injected into the job as an environment variable. Running urltrigger 0.47, the string parameter is not getting injected when the urltrigger fires the job. This was working using urltrigger 0.43. We downgraded to 0.43 and this job started working again. The URLTrigger log from 0.47 when failing: Polling started on Jan 29, 2020 10:43:04 AM {{Polling for the job testfoo }} {{Looking nodes where the poll can be run. }} {{Looking for a candidate node to run the poll. }} Trying to find an eligible node with the assigned project label coord. {{Polling remotely on jenkinsserver }} Resolving environment variables using global values {{Using Basic Authentication with the user 'build' }} {{Invoking the url: }}{{[https://jenkinsserver.foo.com/job/test/job/test/job/testing/lastSuccessfulBuild/buildNumber/
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title John Lengeling reopened an issue We are seeing the pingthread killing xunit processsing as described. Provided stacktrace and error mesages. Jenkins / JENKINS-52842 xUnit plugin blocks PingThread responses Change By: John Lengeling Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title
John Lengeling commented on JENKINS-52842
Re: xUnit plugin blocks PingThread responses
Nikolas, Looks like I have run into this issue. We generate a lot of XML files..sometimes 800+. Looks like the ping thread killed it. We are running Jenkins 2.204.1 and xunit 2.37. Is there a workaround or a snapshot to test? Thanks! Error message: Processing xunit results failed, archiving test result files foo/wr8-64/build/_TestArtifacts*/*.xml for troubleshooting [Pipeline] archiveArtifacts 10:07:27 EC2 (foo-es-aws) - team-foo.fooTool-large (i-06488c01860a95d82) was marked offline: Connection was broken: java.util.concurrent.TimeoutException: Ping started at 1580227324607 hasn't completed by 1580227564613 10:07:27 at hudson.remoting.PingThread.ping(PingThread.java:133) 10:07:27 at hudson.remoting.PingThread.run(PingThread.java:89) {{10:07:27 }} {{[Pipeline] }}} [Pipeline] // script Error when executing always post condition: java.lang.IllegalArgumentException: Failed to prepare archiveArtifacts step {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeDescribable(DSL.java:419)}} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:182)}} {{ at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)}} {{ at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48)}} {{ at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)}} {{ at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)}} {{ at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)}} {{ at com.fooCorp.pipeline.fooTool.publishUnitTests(fooTool.groovy:597)}} {{ at com.fooCorp.pipeline.fooTool.publishfooToolReports(fooTool.groovy:666)}} {{ at com.fooCorp.pipeline.fooTool.publish(fooTool.groovy:610)}} {{ at WorkflowScript.run(WorkflowScript:61)}} {{ at __cps.transform__(Native Method)}} {{ at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)}} {{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)}} {{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)}} {{ at sun.reflect.GeneratedMethodAccessor960.invoke(Unknown Source)}} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}} {{ at java.lang.reflect.Method.invoke(Method.java:498)}} {{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)}} {{ at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55)}} {{ at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45)}} {{ at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source)}} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}} {{ at java.lang.reflect.Method.invoke(Method.java:498)}} {{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)}} {{ at com.cloudbees.groovy.cps.impl.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39)}} {{ at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)}} {{ at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28)}} {{ at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55)}} {{ at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16)}} {{ at com.cloudbees.groovy.cps.Next.step(Next.java:83)}} {{ at
[JIRA] (JENKINS-56446) IOException in FileLogStorage maybeFlush
Title: Message Title
John Lengeling commented on JENKINS-56446
Re: IOException in FileLogStorage maybeFlush
Ran into this issue under Jenkins 2.176.3 with workflow-api 2.37, mailer 1.27 , email-ext 2.66. It occurred thou in the job post section trying to send an email notification. Over a couple of days, the stacktraces filled up the partition since it outputs about every 30s-60s. Tried to abort the job but it would not die. Tried to kill the thread from Melody but it would not die. Had to restart Jenkins and the job started running again after the restart. Then I quickly killed it. ``` {{Sep 25, 2019 8:22:34 AM org.jenkinsci.plugins.workflow.log.FileLogStorage maybeFlush WARNING: failed to flush /opt/apache/.jenkins/jobs/Reprogramming/jobs/verify/branches/master/builds/604/log java.io.IOException: Stream Closed at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:326) at org.jenkinsci.plugins.workflow.log.DelayBufferedOutputStream$FlushControlledOutputStream.write(DelayBufferedOutputStream.java:129) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) at java.io.FilterOutputStream.flush(FilterOutputStream.java:140) at org.jenkinsci.plugins.workflow.log.FileLogStorage.maybeFlush(FileLogStorage.java:190) at org.jenkinsci.plugins.workflow.log.FileLogStorage.overallLog(FileLogStorage.java:198) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogText(WorkflowRun.java:1019) at hudson.plugins.emailext.AttachmentUtils$LogFileDataSource.getInputStream(AttachmentUtils.java:100) at javax.mail.internet.MimeUtility.getEncoding(MimeUtility.java:197) at javax.mail.internet.MimeUtility.getEncoding(MimeUtility.java:256) at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1366) at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1021) at javax.mail.internet.MimeMultipart.updateHeaders(MimeMultipart.java:419) at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1345) at javax.mail.internet.MimeMessage.updateHeaders(MimeMessage.java:2106) at javax.mail.internet.MimeMessage.saveChanges(MimeMessage.java:2074) at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1769) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:484) at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:224) at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:163) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)}} ```
[JIRA] (JENKINS-59233) EC2 Plugin leaking file handles
Title: Message Title
John Lengeling updated an issue
Jenkins / JENKINS-59233
EC2 Plugin leaking file handles
Change By:
John Lengeling
*When the Github Org Folder Scan runs and tries to clean up old branch and PR builds, we see errors like this ".nfsX : Device or Resource Busy". See stack trace below: * {{FATAL: Failed to recompute children of Bluton Pull Requests » bluton}}{{jenkins.util.io.CompositeIOException: Unable to delete '/opt/apache/.jenkins/jobs/Bluton Pull Requests/jobs/bluton/branches/Docker123'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.}} \ {{ at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:95)}} \ {{ at hudson.Util.deleteRecursive(Util.java:294)}} \ {{ at hudson.Util.deleteRecursive(Util.java:283)}} \ {{ at hudson.model.AbstractItem.performDelete(AbstractItem.java:792)}} \ {{ at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:652)}} \ {{ at hudson.model.AbstractItem.delete(AbstractItem.java:776)}} \ {{ at hudson.model.Job.delete(Job.java:677)}} \ {{ at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290)}} \ {{ at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)}} \ {{ at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025)}} \ {{ at hudson.model.ResourceController.execute(ResourceController.java:97)}} \ {{ at hudson.model.Executor.run(Executor.java:429)}}{{jenkins.util.io.CompositeIOException: Unable to remove file /opt/apache/.jenkins/jobs/Bluton Pull Requests/jobs/bluton/branches/Docker123/builds/41/.nfs080f5285009d}} \ {{ at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:248)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:201)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:212)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)}} \ {{ at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)}} \ {{ at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:92)}} \ {{ at hudson.Util.deleteRecursive(Util.java:294)}} \ {{ at hudson.Util.deleteRecursive(Util.java:283)}} \ {{ at hudson.model.AbstractItem.performDelete(AbstractItem.java:792)}} \ {{ at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:652)}} \ {{ at hudson.model.AbstractItem.delete(AbstractItem.java:776)}} \ {{ at hudson.model.Job.delete(Job.java:677)}} \ {{ at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290)}} \ {{ at
[JIRA] (JENKINS-59233) EC2 Plugin leaking file handles
Title: Message Title
John Lengeling created an issue
Jenkins / JENKINS-59233
EC2 Plugin leaking file handles
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-09-04 18:27
Environment:
Jenkins 1.164.1 EC2 Plugin: 1.42
Labels:
filehandle-leak
Priority:
Minor
Reporter:
John Lengeling
When the Github Org Folder Scan runs and tries to clean up old branch and PR builds, we see errors like this: FATAL: Failed to recompute children of Bluton Pull Requests » bluton jenkins.util.io.CompositeIOException: Unable to delete '/opt/apache/.jenkins/jobs/Bluton Pull Requests/jobs/bluton/branches/Docker123'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. {{ at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:95)}} {{ at hudson.Util.deleteRecursive(Util.java:294)}} {{ at hudson.Util.deleteRecursive(Util.java:283)}} {{ at hudson.model.AbstractItem.performDelete(AbstractItem.java:792)}} {{ at org.jenkinsci.plugins.workflow.job.WorkflowJob.performDelete(WorkflowJob.java:652)}} {{ at hudson.model.AbstractItem.delete(AbstractItem.java:776)}} {{ at hudson.model.Job.delete(Job.java:677)}} {{ at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:290)}} {{ at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)}} {{ at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025)}} {{ at hudson.model.ResourceController.execute(ResourceController.java:97)}} {{ at hudson.model.Executor.run(Executor.java:429)}}
[JIRA] (JENKINS-57215) Plugin starts a worked and might immediately stop it, because of cached EC2Computer.getUptime()
Title: Message Title John Lengeling commented on JENKINS-57215 Re: Plugin starts a worked and might immediately stop it, because of cached EC2Computer.getUptime() I ran into this issue using version 1.42/1.43 of the plugin when running a large job that wants to provision 100+ nodes. I see the PR is approved now, if someone and can get a snapshot build, I will test it out. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198972.1556526924000.4657.1561042920167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55084) Cloud Statistics does not show EC2 instance information
Title: Message Title John Lengeling created an issue Jenkins / JENKINS-55084 Cloud Statistics does not show EC2 instance information Issue Type: Improvement Assignee: Oliver Gondža Components: cloud-stats-plugin, ec2-plugin Created: 2018-12-07 18:03 Environment: jenkins: 2.138.2 cloud-stats-plugin: 0.19 ec2-plugin: 1.41 Labels: cloud ec2 aws Priority: Minor Reporter: John Lengeling We are using the cloud-stats-plugin to monitor issues spinning up openstack instances. Cloud Statistics show any errors spinning up elastic build nodes. We recently added the ec2-plugin and noticed that the cloud-stats-plugin does not interface or show any information about our EC2 elastic build nodes. Support for ec2 instances under cloud statistics is important is it is the main interface to monitor errors spinning up elastic nodes used with Jenkins.
[JIRA] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title John Lengeling commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module We haven't seen the issue on any of our 10+ jenkins severs since we started running Java 1.7.80. Would be interesting if you see the problem under that version of java. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title John Lengeling commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module We were running into this issue after we upgraded to Java 1.8.60 in January with Jenkins 1.632. We downgraded to Java on the master to 1.7.80 and the "iota" errors went away. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
