[JIRA] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Emory Penney commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes I tried 2.32.3 with Oracle JDK8 today, issue persists. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38834 Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Change By: Oleg Nenashev Component/s: perforce-plugin 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38834 Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Change By: Oleg Nenashev Labels: regression 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Greg Smith commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes We were able to recreate this problem with per-anniversary edition of Windows 10, so its not related to that. It looks like this might be related to https://issues.jenkins-ci.org/browse/JENKINS-19445 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Greg Smith commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes I believe the difference between my environment (where this hang causes all builds to stall) and your environment (where only that single node stalls) - is that we are using Pipeline builds, where you are using freestyle builds. As part of the code for a pipeline build runs on the master, this hang seems to block all other activity on the master. That makes it a bit worse in the scenario where Pipeline is being used – but either way, its very bad. 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Emory Penney commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes That appears to be the case, all affected nodes are Win10 AE, but not all of my Win10 AE nodes are affected. It doesn't look like the affliction is consistent: Sometimes jobs will run fine on these nodes, sometimes they won't. 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Daniel Beck commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes To clarify, all affected nodes run Windows 10 Anniversary Edition, but not all nodes running Windows 10 Anniversary Edition are affected by this issue (despite running the same kinds of jobs)? 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Emory Penney commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Yes all running Windows 10 Anniversary Edition. Luckily for us the issue remains isolated to specific nodes, and other jobs seem to run unimpeded. As I said above, downgrading to 2.7.4 made the issue disappear for me! 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Greg Smith commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Are all of your Windows 10 machines updated to the anniversary edition? For us, it is happening and locking up all builds. If you find the build with the JNI stack, you can kill that single slave, and all other slaves will be able to continue. 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Greg Smith commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Your stack seems to be pretty similar to mine, in this bug: https://issues.jenkins-ci.org/browse/JENKINS-39179 That bug is driving me and my team crazy. They could be the same. 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Emory Penney commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Jenkins ThreadDump from one of our hung executors: Executor #0 for GJ-WTX64-S05V13 : executing jenkins_admin_component_1 #25147 / waiting for hudson.remoting.Channel@45b513d2:GJ-WTX64-S05V13 "Executor #0 for GJ-WTX64-S05V13 : executing jenkins_admin_component_1 #25147 / waiting for hudson.remoting.Channel@45b513d2:GJ-WTX64-S05V13" Id=204 Group=main TIMED_WAITING on hudson.remoting.UserRequest@33f1c9bd at java.lang.Object.wait(Native Method) waiting on hudson.remoting.UserRequest@33f1c9bd at hudson.remoting.Request.call(Request.java:147) at hudson.remoting.Channel.call(Channel.java:796) at hudson.FilePath.act(FilePath.java:1007) at hudson.FilePath.act(FilePath.java:996) at hudson.FilePath.deleteRecursive(FilePath.java:1198) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:934) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1720) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) ThreadDump from that server: Channel reader thread: channel "Channel reader thread: channel" Id=2301 Group=main RUNNABLE (in native) at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) locked java.io.BufferedInputStream@40bda018 at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:86) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) main "main" Id=1 Group=main WAITING on hudson.remoting.Engine@a3d1956 at java.lang.Object.wait(Native Method) waiting on hudson.remoting.Engine
[JIRA] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Emory Penney commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Will do, I tried today to reproduce it in a non-production environment unsuccessfully. I'm working on deploying a clone of our production environment now, but it could take a few days... 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Daniel Beck commented on JENKINS-38834 Re: Freestyle jobs hang in 2.19.1 on Windows 10 Nodes While it appears to hang, create a thread dump: https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump 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] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Emory Penney created an issue Jenkins / JENKINS-38834 Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/07 8:52 PM Environment: Jenkins 2.19.1 on Ubuntu 14.04 x64 Windows 10 (1607) Connected via JNLP Priority: Critical Reporter: Emory Penney Freestyle jobs hang either at the beginning or the end of execution. I've let a few run for ~18 hours before they eventually crash with errors like these: 07:52:37 java.io.IOException: Unable to get hostname from slave. null 07:52:37 at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:1187) 07:52:37 at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 07:52:37 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) 07:52:37 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 07:52:37 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 07:52:37 at hudson.model.Run.execute(Run.java:1720) 07:52:37 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 07:52:37 at hudson.model.ResourceController.execute(ResourceController.java:98) 07:52:37 at hudson.model.Executor.run(Executor.java:404) Reverting back to Jenkins 2.7.4 immediately resolved the issue. Issue was not observed with any Linux/OSX/older Windows nodes.
