These are too many warnings for the current architecture of the plug-in, see 
https://issues.jenkins-ci.org/browse/JENKINS-1960 
<https://issues.jenkins-ci.org/browse/JENKINS-1960>.

Once the refactoring to the new analysis-model is finished, I think it would be 
possible to add an option to just count the number of warnings rather then 
creating and persisting them.

BTW: what is the reason that you are interested in tracking so many warnings?

> Am 09.02.2018 um 12:39 schrieb Consult Hyperion * <chyp...@gmail.com>:
> 
> At the last count:
> 
> 42938 Warning(s)
> 
> I did wonder if that was just too many and it was overloading something.  Is 
> that the problem?
> 
> 
> On Thursday, February 8, 2018 at 5:16:52 PM UTC, Ullrich Hafner wrote:
> How many warnings do you have?
> 
>> Am 08.02.2018 um 18:01 schrieb Consult Hyperion * <chy...@gmail.com <>>:
>> 
>> I keep getting this on a job - the worker is fine with other jobs:
>> 
>> [WARNINGS] Parsing warnings in console log with parser MSBuild
>> Skipping warnings blame since Git is the only supported SCM up to now.%n
>> FATAL: Java heap space
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.HashMap.resize(Unknown Source)
>> at java.util.HashMap.putVal(Unknown Source)
>> at java.util.HashMap.put(Unknown Source)
>> at java.util.HashSet.add(Unknown Source)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addCategory(AnnotationContainer.java:285)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:250)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAuthorName(AnnotationContainer.java:393)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:267)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addModule(AnnotationContainer.java:319)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:256)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotations(AnnotationContainer.java:376)
>> at hudson.plugins.analysis.core.BuildResult.initialize(BuildResult.java:307)
>> at hudson.plugins.analysis.core.BuildResult.<init>(BuildResult.java:222)
>> at hudson.plugins.warnings.WarningsResult.<init>(WarningsResult.java:52)
>> at hudson.plugins.warnings.WarningsResult.<init>(WarningsResult.java:46)
>> at 
>> hudson.plugins.warnings.WarningsPublisher.annotate(WarningsPublisher.java:434)
>> at 
>> hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:378)
>> at 
>> hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:312)
>> at 
>> hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69)
>> at 
>> hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:298)
>> at 
>> hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
>> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
>> at hudson.model.Build$BuildExecution.post2(Build.java:186)
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
>> at hudson.model.Run.execute(Run.java:1749)
>> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>> at hudson.model.ResourceController.execute(ResourceController.java:97)
>> 
>> I've tried increasing the heap space (I think) with -Xmx2048M on the worker 
>> but it's not helping.  I'm wondering if the problem might be on the server 
>> instead?  It seems to start parsing warnings, get some of the way through 
>> then fall over.  Any useful suggestions gratefully received.
>> 
>> Thanks.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/f079111d-0efb-4cff-a304-b4b6db3252d8%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/f079111d-0efb-4cff-a304-b4b6db3252d8%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/0bd305d4-cf4c-49a9-8047-98ce57717980%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/0bd305d4-cf4c-49a9-8047-98ce57717980%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D45B1AA0-32E3-4ADD-97AA-48969DAB8987%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to