[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output

2019-03-04 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JavaDocParser is slow at parsing the log output   
 

  
 
 
 
 

 
 Ok PR is there, have implemented a more generic solution, hope you like it.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output

2019-03-04 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JavaDocParser is slow at parsing the log output   
 

  
 
 
 
 

 
 Should i prepare a PR?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output

2019-03-04 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JavaDocParser is slow at parsing the log output   
 

  
 
 
 
 

 
 Looks like my theory is correct, the regex is the show stopper. What do you think about limiting the content that is inspected by the regex. Did some tests and limiting the length to 4000 chars cures all the problems without failing tests. Optional 
 
every subclass can provide a length restriction (default none) 
every subclass can restrict the line (default is to return the whole line) 
every subclass can overwrite the match and limit the line before calling the matcher 
 What do you think?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output

2019-03-04 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JavaDocParser is slow at parsing the log output   
 

  
 
 
 
 

 
 Ok will have a look.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output

2019-03-04 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JavaDocParser is slow at parsing the log output   
 

  
 
 
 
 

 
 Another option: Use https://www.brics.dk/automaton/ as regex engine. Have done this successfully in the past for Wetator to increase performance.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output

2019-03-04 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JavaDocParser is slow at parsing the log output   
 

  
 
 
 
 

 
 Made already a suggestion: Maybe using the regex with the first e.g. 400 chars of a line to make sure this is a candidate for a deeper analysis is an option to make the parser faster. But if you like i can have a deeper look.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-03-04 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
 Any update on this? Thanks for your support.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-02-08 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
 Not sure witch parser is the problem. See the log output from one week ago. For me it looks like the javadoc parser is now the problem.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-02-08 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Sorry but after updating to the latest version of the analysis and warnings ng plugin i still have the 10 minutes delay for parsing.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55805  
 
 
  Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
Change By: 
 Ronald Brill  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-01-31 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
 Maybe using the regex with the first e.g. 400 chars of a line to make sure this is a candidate for a deeper analysis is an option to make the parser faster.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-01-31 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
 Have removed the Java parser, not the JavaDoc parser is the blocker 20:39:49 [JavaDoc] Sleeping for 5 seconds due to JENKINS-32191... 20:39:54 [JavaDoc] Parsing console log (workspace: '/var/lib/jenkins/workspace/HtmlUnit') 20:50:24 [JavaDoc] Attaching ResultAction with ID 'javadoc-warnings' to run 'HtmlUnit #268'. 20:50:24 [JavaDoc] Using reference build 'HtmlUnit #267' to compute new, fixed, and outstanding issues 20:50:24 [JavaDoc] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 20:50:24 [JavaDoc] No quality gates have been set - skipping 20:50:24 [JavaDoc] Health report is disabled - skipping 20:50:24 [JavaDoc] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-01-28 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill edited a comment on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
 Thanks  fr  for  looking at this.Yes, java and a bunch of PMD Spotbugs and all that stuff. Will provide more details but In detail:* Java* Checkstyle* JavaDoc* PMD* CPD* SpotbugsAll with  the  jenkins does not respond at the moment (i guess the parser hooks the whole server right now)  default settings .  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-01-27 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill commented on  JENKINS-55805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
 Thanks fr looking at this. Yes, java and a bunch of PMD Spotbugs and all that stuff. Will provide more details but the jenkins does not respond at the moment (i guess the parser hooks the whole server right now).  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-01-27 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55805  
 
 
  Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
Change By: 
 Ronald Brill  
 

  
 
 
 
 

 
 First of all, the new plugin is great.Some days ago i noticed a major change in the build performance of my project (http://83.169.43.181/jenkins/job/HtmlUnit/). After some checking i found that this is because the parsing of the output takes really long.19:43:09 [Java] Sleeping for 5 seconds due to JENKINS-32191...19:43:14 [Java] Parsing console log (workspace: '/var/lib/jenkins/workspace/HtmlUnit')19:59:59 [Java] Attaching ResultAction with ID 'java' to run 'HtmlUnit #262'.19:59:59 [Java] Using reference build 'HtmlUnit #261' to compute new, fixed, and outstanding issues19:59:59 [Java] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 019:59:59 [Java] No quality gates have been set - skipping19:59:59 [Java] Health report is disabled - skipping19:59:59 [Java] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Yes the log is really long, but this was not a problem in the past. With a bit more testing i found out that the log contains two really long lines with _javascript_ inside. Looks like this lines are killing the parser.Have attached the critical lines.This is a log output for a fast run (one without the js lines nothing else changed).22:37:19 [Java] Sleeping for 5 seconds due to JENKINS-32191...22:37:24 [Java] Parsing console log (workspace: '/var/lib/jenkins/workspace/HtmlUnit')22:37:24 [Java] Attaching ResultAction with ID 'java' to run 'HtmlUnit #263'.22:37:24 [Java] Using reference build 'HtmlUnit #262' to compute new, fixed, and outstanding issues22:37:24 [Java] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 022:37:24 [Java] No quality gates have been set - skipping22:37:24 [Java] Health report is disabled - skipping22:37:24 [Java] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) If you like i can provide the whole log also.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output

2019-01-27 Thread r...@rbri.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronald Brill created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55805  
 
 
  Warnings Next Generation Plugin is slow at parsing the log output   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ulli Hafner  
 
 
Attachments: 
 build_output.txt  
 
 
Components: 
 warnings-ng-plugin  
 
 
Created: 
 2019-01-27 13:04  
 
 
Environment: 
 Plugin version 2.1.1  Jenkins 2.150.2  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronald Brill  
 

  
 
 
 
 

 
 First of all, the new plugin is great. Some days ago i noticed a major change in the build performance of my project (http://83.169.43.181/jenkins/job/HtmlUnit/). After some checking i found that this is because the parsing of the output takes really long. 19:43:09 [Java] Sleeping for 5 seconds due to JENKINS-32191... 19:43:14 [Java] Parsing console log (workspace: '/var/lib/jenkins/workspace/HtmlUnit') 19:59:59 [Java] Attaching ResultAction with ID 'java' to run 'HtmlUnit #262'. 19:59:59 [Java] Using reference build 'HtmlUnit #261' to compute new, fixed, and outstanding issues 19:59:59 [Java] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 19:59:59 [Java] No quality gates have been set - skipping 19:59:59 [Java] Health report is disabled - skipping 19:59:59 [Java] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) Yes the log is really long, but this was not a problem in the past. With a bit more testing i found out that the log contains two really long lines with _javascript_ inside. Looks like this lines are killing the parser. Have attached the critical lines. This is a log output for a fast run (one without the js lines nothing else changed). 22:37:19