crash plug-in warning - java heap space

[iostrym]

Hi,

We did a crash with jenkins, using plug-in warnings with a logfile that is 70 Mo big :

[WARNINGS] Parsing warnings in console log with parser FPGA_Questa_UVM

ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception

hudson.util.IOException2: remote file operation failed: /*******/******** at hudson.remoting.Channel@******:serveur_linux_rdo

  at hudson.FilePath.act(FilePath.java:861)

  at hudson.FilePath.act(FilePath.java:838)

  at hudson.plugins.warnings.WarningsPublisher.annotate(WarningsPublisher.java:447)

  at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:411)

  at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:320)

  at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333)

  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)

  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814)

  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786)

  at hudson.model.Build$BuildExecution.post2(Build.java:183)

  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733)

  at hudson.model.Run.execute(Run.java:1592)

  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)

  at hudson.model.ResourceController.execute(ResourceController.java:88)

  at hudson.model.Executor.run(Executor.java:237)

Caused by: java.io.IOException: Remote call on serveur_linux_rdo failed

  at hudson.remoting.Channel.call(Channel.java:681)

  at hudson.FilePath.act(FilePath.java:854)

  ... 14 more

Caused by: java.lang.OutOfMemoryError: Java heap space

We tried to re-run our slave with a bigger heap size but it doesn't help. So we wonder if the HEAP error is regarding the master or the slave ? Which one is executing the plug-in warning and do the parsing : master or slave ?

because of "Remote call on serveur_linux_rdo failed" we thought that the parsing was done by the slave but as the upgrade of the heap size of  Java Virtual Machine don't change anything and also because I succeed to crash the master and shutdown all slaves connected to the master by testing it, I gives me the feeling that the master may do something with the parsing.

Any idea ?

Best regards,

Armand

[Ullrich Hafner]

Parsing is done on the master.

--
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/8f34dbbe-ec3f-4877-a17d-de3d8b21e9ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[iostrym]

thanks a lot. So the message we have is a java heap problem that occurs on Jenkins Master ? Right ? 

Is it possible to modify the heap size of the Jenkins Master ?

Le samedi 23 janvier 2016 14:18:54 UTC+1, Ullrich Hafner a écrit :

Parsing is done on the master.

Am 22.01.2016 um 14:45 schrieb iostrym <arman...@gmail.com>:

Hi,

We did a crash with jenkins, using plug-in warnings with a logfile that is 70 Mo big :

[WARNINGS] Parsing warnings in console log with parser FPGA_Questa_UVM

ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception

hudson.util.IOException2: remote file operation failed: /*******/******** at hudson.remo...@******:serveur_linux_rdo