[JIRA] (JENKINS-17132) Warnings plugin stuck parsing the console with a regex and blocks other builds using the same plugin to complete

[jhu...@java.net (JIRA)]

jhurne
 created  JENKINS-17132


Warnings plugin stuck parsing the console with a regex and blocks other builds using the same plugin to complete















Issue Type:


Bug



Assignee:


Ulli Hafner



Attachments:


warnings-plugin-thread-dump.txt



Components:


warnings



Created:


08/Mar/13 5:10 PM



Description:


Some of our builds are getting "stuck" when running the Warnings plugin during the publish phase of the build. The builds affected are configured to use the "Javac (Eclipse)" parser and the "Javadoc" parser. The parsers are configured against the console log only.

When a build gets stuck running the Warnings plugin, any other build that also uses the Warnings plugin and is running at about the same time also gets stuck.  Eventually, all of our slaves are consumed with builds stuck at the warnings plugin step and no further builds can be built.

We are able to kill all of the builds except the one build which triggered the problem. In order to kill the original build we end up restarting the entire Jenkins system.

We did some investigation and it appears that the Warnings plugin is getting stuck while using a regular _expression_ to parse the console log.  The thread dump of Jenkins shows that the Warnings plugin has a deep stack running a regular _expression_ (see attached), and a quick peak at the system itself shows that the plugin is consuming 100% of one of our server's cpu cores.

It is clear from the thread stack and the build console log that the plugin is getting stuck when using the "Java (Eclipse)" plugin.

We know there have been problems in the past with parsing very large logs or files, however, the build console log is not very large (23kb).

We let the stuck build run for about 18 hours before we decided to kill it. We know the plugin was doing work (a) because the CPU core was pegged at 100%, and (b) the stack trace for the plugin worker thread would change periodically.




Environment:


Jenkins 1.480.3 running on Oracle Java version 1.7.0_03-b04 on 64-bit Linux

Warnings Plugin 4.32




Project:


Jenkins



Labels:


warnings




Priority:


Major



Reporter:


jhurne

























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/groups/opt_out.

[JIRA] (JENKINS-17132) Warnings plugin stuck parsing the console with a regex and blocks other builds using the same plugin to complete

[docw...@gerf.org (JIRA)]

Christian Höltje
 commented on  JENKINS-17132


Warnings plugin stuck parsing the console with a regex and blocks other builds using the same plugin to complete















We can try to sanitize the log file so we can post it. (I work with jhurne)

Better would be tell us what you're looking for and we can post just that.  Or if you have tests you'd like us to run (like a raw regex) we can run that.

It's also worth mentioning that we weren't sure why it was set to the Eclipse parser.  We have switched that build to use the javac parser instead, because we're just doing a straight maven build.  I'm not even sure how you can compile in Jenkins with Eclipse.



























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/groups/opt_out.