Parsing is done on the master. > Am 22.01.2016 um 14:45 schrieb iostrym <[email protected]>: > > 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 > <http://stacktrace.jenkins-ci.org/search?query=hudson.util.IOException2>: > remote file operation failed: /*******/******** at > hudson.remoting.Channel@******:serveur_linux_rdo > <mailto:hudson.remoting.Channel@3b0ff171:eSAC_serveur_linux_rdo> > at hudson.FilePath.act(FilePath.java:861) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.act&entity=method> > at hudson.FilePath.act(FilePath.java:838) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.act&entity=method> > at > hudson.plugins.warnings.WarningsPublisher.annotate(WarningsPublisher.java:447) > > <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.warnings.WarningsPublisher.annotate&entity=method> > at > hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:411) > > <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.warnings.WarningsPublisher.parseConsoleLog&entity=method> > at > hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:320) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.warnings.WarningsPublisher.perform&entity=method> > at > hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) > > <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.analysis.core.HealthAwareRecorder.perform&entity=method> > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.tasks.BuildStepMonitor$1.perform&entity=method> > at > hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) > > <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.perform&entity=method> > at > hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786) > > <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps&entity=method> > at hudson.model.Build$BuildExecution.post2(Build.java:183) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.post2&entity=method> > at > hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733) > > <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.post&entity=method> > at hudson.model.Run.execute(Run.java:1592) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method> > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.run&entity=method> > at hudson.model.ResourceController.execute(ResourceController.java:88) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method> > at hudson.model.Executor.run(Executor.java:237) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method> > Caused by: java.io.IOException > <http://stacktrace.jenkins-ci.org/search?query=java.io.IOException>: Remote > call on serveur_linux_rdo failed > at hudson.remoting.Channel.call(Channel.java:681) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.call&entity=method> > at hudson.FilePath.act(FilePath.java:854) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.act&entity=method> > ... 14 more > Caused by: java.lang.OutOfMemoryError > <http://stacktrace.jenkins-ci.org/search?query=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 > > -- > 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 [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/8f34dbbe-ec3f-4877-a17d-de3d8b21e9ed%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-users/8f34dbbe-ec3f-4877-a17d-de3d8b21e9ed%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/50303681-211F-4058-B93C-4582E3FBBB45%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
