[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
SCM/JIRA link daemon commented on JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Code changed in jenkins User: Stephen Connolly Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/0cfa00d1e7f0dd91d2aa0998e226c986636c3e7b Log: FIXED JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis (cherry picked from commit 7c620e9fd321029e05f7cc994d3da1dde48411f7) Conflicts: changelog.html 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
boris ivan commented on JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Regarding the "== Why someone would have 4MB of stderr output ==" Many of us use Jenkins for things like running Maven builds which have a goal of "integration-test". In other words, there is very little 'build' in the traditional sense, but instead reams and reams of output from testNG tests, etc, and there might be a valid reason to use stderr. Couple that with potentially thousands of tests... Just adding this commentary in case it helps people think of scenarios like this. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
boris ivan edited a comment on JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Regarding the "== Why someone would have 4MB of stderr output ==" Some of us use Jenkins for things like running Maven builds which have a goal of "integration-test". In other words, there is very little 'build' in the traditional sense, and in fact the 'build' itself may not even be unit tests associated with a build of a product-under-test, but an entirely separate test project being built that interacts with something completely external. This generates reams and reams of output from testNG tests, etc, and there might be a valid reason to use stderr in some of that output. Couple that with potentially thousands of tests... Just adding this commentary in case it helps people think of scenarios like this. We use it in this fashion nightly. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
SCM/JIRA link daemon commented on JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Code changed in jenkins User: Stephen Connolly Path: src/com/trilead/ssh2/channel/Channel.java http://jenkins-ci.org/commit/trilead-ssh2/5811ddd7ae15670a4f9ad345352613b3f2f2db97 Log: JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis The fix for JENKINS-18836, JENKINS-18879, JENKINS-19619 was incorrect in its analysis. There is no call to getChannelData() on the new code path, so thus you cannot have two calls of freeupWindow() The problem with the original call to freeupWindow() is that it is on the receiver thread. You should not mix the responsibilities. Blocking the receiver thread to send a message will negatively impact performance and connection stability. The correct solution is to push the freeupWindow onto the async queue thus the ACK gets sent and the purity of the receiving thread can be maintained. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
SCM/JIRA link daemon commented on JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Code changed in jenkins User: Stephen Connolly Path: changelog.html core/pom.xml http://jenkins-ci.org/commit/jenkins/7c620e9fd321029e05f7cc994d3da1dde48411f7 Log: FIXED JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
SCM/JIRA link daemon resolved JENKINS-22938 as Fixed SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Change By: SCM/JIRA link daemon (19/May/14 4:54 PM) Status: Open Resolved Resolution: Fixed 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
stephenconnolly assigned JENKINS-22938 to stephenconnolly SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Change By: stephenconnolly (14/May/14 9:15 AM) Assignee: KohsukeKawaguchi stephenconnolly 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
stephenconnolly commented on JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis There is a 3rd path. Call freeupWindow, but from the async message queue which retains the purity of the receiver thread. Implemented in build217-jenkins-5 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
stephenconnolly commented on JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis https://github.com/jenkinsci/trilead-ssh2/commit/5811ddd7ae15670a4f9ad345352613b3f2f2db97 https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
stephenconnolly updated JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Change By: stephenconnolly (14/May/14 9:19 AM) Labels: lts-candidate 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-22938) SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis
dogfood commented on JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis Integrated in jenkins_main_trunk #3380 FIXED JENKINS-22938 SSH slave connections die after the slave outputs 4MB of stderr, usually during findbugs analysis (Revision 7c620e9fd321029e05f7cc994d3da1dde48411f7) Result = SUCCESS Stephen Connolly : 7c620e9fd321029e05f7cc994d3da1dde48411f7 Files : core/pom.xml changelog.html 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
