[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27664 Re: Job hanging, killing not possible Code changed in jenkins User: Tobias Gruetzmacher Path: src/main/java/hudson/plugins/warnings/parser/EclipseParser.java src/test/java/hudson/plugins/warnings/parser/EclipseParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue27664.txt http://jenkins-ci.org/commit/warnings-plugin/167f35f42c58b0a587a3def816ab9ea54792d84f Log: JENKINS-27664 Better Performance of EclipseParser. Tune the regular _expression_ used in the EclipseParser to not backtrack through the whole log output. 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27664 Re: Job hanging, killing not possible Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/EclipseParser.java src/test/java/hudson/plugins/warnings/parser/EclipseParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue27664.txt http://jenkins-ci.org/commit/warnings-plugin/c3f5088ba82fd59f7bf60fec15255b4ccf455832 Log: Merge pull request #72 from TobiX/eclipse-parser-performance [FIXED JENKINS-27664] Improved performance of EclipseParser. Compare: https://github.com/jenkinsci/warnings-plugin/compare/6b50ca13c489...c3f5088ba82f 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-27664 Job hanging, killing not possible Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible This fix looks promising! I'm looking forward for the PR 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title
Tobias Gruetzmacher edited a comment on JENKINS-27664
Re: Job hanging, killing not possible
I think I found a problem in the EclipseParser RegEx, which is quite easy to fix:{code}[^\\^]*{code}matches newlines, creating a RegEx that has to scan the whole remaining file for each possible match up to this point. Changing this to:{code}[^\\n\\^]*{code}confines the match to the current line and fixes the quadratic runtime. Maybe add a test with timeout ({code:java}@Test(timeout = 1){code}) which parses my attached testcase as a verification.Oh, and thanks for the awesome Jenkins plugin(s) :)(Shout out to https://regex101.com/ for helping me find this problem)PS: - Quite "interesting" to see how the Eclipse Parser parses javac into totally wrong errors, but that is probably a new bug... -PPS: Scratch that, I made an error. There are some other oddities in that regular _expression_ (1-character character-groups, useless non-capture groups). It would also probably not hurt to restrict the search space for the "marker line" (line only with ^ chars) to maybe ~5 lines. I'll send a pull request this evening.
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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title
Tobias Gruetzmacher edited a comment on JENKINS-27664
Re: Job hanging, killing not possible
I think I found a problem in the EclipseParser RegEx, which is quite easy to fix:{code}[^\\^]*{code}matches newlines, creating a RegEx that has to scan the whole remaining file for each possible match up to this point. Changing this to:{code}[^\\n\\^]*{code}confines the match to the current line and fixes the quadratic runtime. Maybe add a test with timeout ({code:java}@Test(timeout = 1){code}) which parses my attached testcase as a verification.Oh, and thanks for the awesome Jenkins plugin(s) :)(Shout out to https://regex101.com/ for helping me find this problem) PS: Quite "interesting" to see how the Eclipse Parser parses javac into totally wrong errors, but that is probably a new bug...
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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Tobias Gruetzmacher commented on JENKINS-27664 Re: Job hanging, killing not possible I think I found a problem in the EclipseParser RegEx, which is quite easy to fix: [^\\^]* matches newlines, creating a RegEx that has to scan the whole remaining file for each possible match up to this point. Changing this to: [^\\n\\^]* confines the match to the current line and fixes the quadratic runtime. Maybe add a test with timeout ( @Test(timeout = 1) ) which parses my attached testcase as a verification. Oh, and thanks for the awesome Jenkins plugin(s) (Shout out to https://regex101.com/ for helping me find this problem) 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible See https://issues.jenkins-ci.org/browse/JENKINS-27664?focusedCommentId=236828=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-236828. 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-27664 Job hanging, killing not possible Here is a simple (20 lines!) sample file that throws the EclipseParser into a quite long loop (> 2 minutes on my system)... And the time grows very fast with the number of lines to parse... Change By: Tobias Gruetzmacher Attachment: eclipse-regex-explosion.txt 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27664 Re: Job hanging, killing not possible And in the end it prints Parsing warnings in console log with parser Java Compiler (javac) null Expected Java Warnings: 0 warnings. 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title
Kanstantsin Shautsou edited a comment on JENKINS-27664
Re: Job hanging, killing not possible
Jenkins 1.609.3, Warnings Plug-in 4.50. Unable to abort job, only jenkins restart. {code}Parsing warnings in console log with parser Java Compiler (javac){code}Log size: 33,645 KB{code}Id=34558 Group=main RUNNABLE at java.util.regex.Pattern$Curly.match0(Pattern.java:4260) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4658) at java.util.regex.Pattern$Curly.match0(Pattern.java:4279) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$Curly.match0(Pattern.java:4279) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$BranchConn.match(Pattern.java:4568) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4717) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3798) at java.util.regex.Pattern$Curly.match0(Pattern.java:4272) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3798) at java.util.regex.Pattern$Curly.match0(Pattern.java:4272) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4658) at java.util.regex.Pattern$Branch.match(Pattern.java:4604) at java.util.regex.Pattern$Begin.match(Pattern.java:3525) at java.util.regex.Pattern$Branch.match(Pattern.java:4604) at java.util.regex.Pattern$Start.match(Pattern.java:3461) at java.util.regex.Matcher.search(Matcher.java:1248) at java.util.regex.Matcher.find(Matcher.java:637) at hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:86) at hudson.plugins.warnings.parser.RegexpLineParser.parse(RegexpLineParser.java:87) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:260) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:324) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:266) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:259) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:776) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1053) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1763) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:537) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){code}
Add Comment
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27664 Re: Job hanging, killing not possible Ulli Hafner is it possible to run this algorithm against log? I can download log to my laptop, but i don't know plugin internals atm 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27664 Re: Job hanging, killing not possible Parsing warnings in console log with parser Java Compiler (javac) Log size: 33,645 KB Id=34558 Group=main RUNNABLE at java.util.regex.Pattern$Curly.match0(Pattern.java:4260) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4658) at java.util.regex.Pattern$Curly.match0(Pattern.java:4279) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$Curly.match0(Pattern.java:4279) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$BranchConn.match(Pattern.java:4568) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4717) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3798) at java.util.regex.Pattern$Curly.match0(Pattern.java:4272) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3798) at java.util.regex.Pattern$Curly.match0(Pattern.java:4272) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4658) at java.util.regex.Pattern$Branch.match(Pattern.java:4604) at java.util.regex.Pattern$Begin.match(Pattern.java:3525) at java.util.regex.Pattern$Branch.match(Pattern.java:4604) at java.util.regex.Pattern$Start.match(Pattern.java:3461) at java.util.regex.Matcher.search(Matcher.java:1248) at java.util.regex.Matcher.find(Matcher.java:637) at hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:86) at hudson.plugins.warnings.parser.RegexpLineParser.parse(RegexpLineParser.java:87) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:260) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:324) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:266) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:259) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:776) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1053) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1763) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:537) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381)
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title
Kanstantsin Shautsou updated an issue
Jenkins / JENKINS-27664
Job hanging, killing not possible
Change By:
Kanstantsin Shautsou
I have a job that keeps hanging everytime it builds. The job ran fine in the past. No changes happend and suddenly it started hanging. ThradDump: {code} Executor #0 for Slave_rlx-v121 : executing m_techlog_reporting/zk.mtr.build #945"Executor #0 for Slave_rlx-v121 : executing m_techlog_reporting/zk.mtr.build #945" Id=79 Group=main RUNNABLE at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4692) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible How long did you wait? 22 MByte is quite a large log file but should be manageable. One problem could be the number of warnings that are generated. How many did you expect? 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27664 Re: Job hanging, killing not possible 4 hours, and can't abort, only jenkins restart helps. Usually build takes 30 min where scan for warnings takes < 1 min. 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible Yes, clone the plug-in and start JavacParserTest and replace the file issue14043.txt with your log file content. 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible Or use the test ParserSpeed to see the speed of each parser. Here you need to fill all.txt with your log file content. 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-27664 Job hanging, killing not possible Change By: Ulli Hafner Priority: Critical Minor 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible The Eclipse warnings parser is quite limited since it needs to parser multiple lines per warning. 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.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Daniel Beck assigned an issue to Ulli Hafner Jenkins / JENKINS-27664 Job hanging, killing not possible Change By: Daniel Beck Component/s: warnings-plugin Component/s: core Assignee: UlliHafner 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.
