[JIRA] [gui] (JENKINS-4561) Delete All Disabled Modules Not visible for project users
vdupain commented on JENKINS-4561 Delete All Disabled Modules Not visible for project users same issue with Jenkins 1.532.1 with projects matrix security strategy. 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/d/optout.
[JIRA] [master-slave] (JENKINS-18921) OutOfMemoryError while serializing test reports to send from salve to master
vdupain created JENKINS-18921 OutOfMemoryError while serializing test reports to send from salve to master Issue Type: Bug Assignee: Unassigned Components: master-slave Created: 25/Jul/13 8:05 AM Description: We have an OutOfMemoryError while serializing test reports to send from salve to master. Build was successfull whereas there are tests failures. In one of the surefire-reports directory, there is more than 400 Mb of files. Workaround was to add more memory to the job (-Xmx2048m to MAVEN_OPTS). [ERROR] There are test failures. Please refer to /data/jenkins-agents/local-slave-2/workspace/MEZZO-pdo-100pro-ps-ci/pdo-100pro-ps-mediation/target/surefire-reports for the individual test results. [JENKINS] Recording test results java.io.IOException: Remote call on channel failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy2.execute(Unknown Source) at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:191) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:160) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:453) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:435) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2786) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
[JIRA] [warnings] (JENKINS-7089) OutOfMemoryError while parsing 11 mb log file
vdupain reopened JENKINS-7089 OutOfMemoryError while parsing 11 mb log file We have the same issue: OutOfMemoryError. Build was successfull whereas there are tests failures. In one of the surefire-reports directory, there is more than 400 Mb of files. Workaround was to add more memory to the job (-Xmx2048m to MAVEN_OPTS). [ERROR] There are test failures. Please refer to /data/jenkins-agents/local-slave-2/workspace/MEZZO-pdo-100pro-ps-ci/pdo-100pro-ps-mediation/target/surefire-reports for the individual test results. [JENKINS] Recording test results java.io.IOException: Remote call on channel failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy2.execute(Unknown Source) at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:191) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:160) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:453) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:435) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2786) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1847) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1756) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1169) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at
[JIRA] [warnings] (JENKINS-7089) OutOfMemoryError while parsing 11 mb log file
vdupain updated JENKINS-7089 OutOfMemoryError while parsing 11 mb log file Change By: vdupain (24/Jul/13 9:21 AM) Environment: WindowsslaveofWindowsmaster ,jenkins1.509.2masterandslavesonLinuxRHEL 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] [dashboard-view] (JENKINS-18880) Build statistics does not display result with regex .* filter
vdupain created JENKINS-18880 Build statistics does not display result with regex .* filter Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Components: dashboard-view Created: 23/Jul/13 8:12 AM Description: Build statistics does not display result with regex .* filter. Exception is thrown: WARNING: Caught exception evaluating: it.getBuildStat(jobs) in /jenkins/view/0.%20Survol/. Reason: java.util.NoSuchElementException java.util.NoSuchElementException at jenkins.model.lazy.AbstractLazyLoadRunMap.firstKey(AbstractLazyLoadRunMap.java:310) at jenkins.model.lazy.AbstractLazyLoadRunMap.firstKey(AbstractLazyLoadRunMap.java:102) at java.util.Collections$UnmodifiableSortedMap.firstKey(Collections.java:1549) at hudson.plugins.view.dashboard.stats.StatBuilds.getBuildStat(StatBuilds.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStati If instead on using regex filter to choose jobs I select job with checkbox, it works, build statistics displays somes results. Environment: Jenkins 1.509.2, RHEL 5 Project: Jenkins Priority: Major Reporter: vdupain 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] [dashboard-view] (JENKINS-18880) Build statistics does not display result with regex .* filter
vdupain updated JENKINS-18880 Build statistics does not display result with regex .* filter Change By: vdupain (23/Jul/13 8:15 AM) Attachment: jenkins_build_statistics.png 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] [dashboard-view] (JENKINS-18880) Build statistics does not display result with regex .* filter
vdupain updated JENKINS-18880 Build statistics does not display result with regex .* filter Change By: vdupain (23/Jul/13 8:16 AM) Environment: Jenkins1.509.2,RHEL5 ,Java1.7.0_09 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] [dashboard-view] (JENKINS-18880) Build statistics does not display result with regex .* filter
vdupain commented on JENKINS-18880 Build statistics does not display result with regex .* filter java.util.NoSuchElementException is throw when job has no build. Pull request: https://github.com/jenkinsci/dashboard-view-plugin/pull/19 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] [configurationslicing] (JENKINS-16328) Configure slicing plugin doesnot work for Delete workspace when build is done
vdupain commented on JENKINS-16328 Configure slicing plugin doesnot work for Delete workspace when build is done So same issue for me with plugin ws-cleanup 0.16 and configurationslicing 1.37: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z at configurationslicing.wscleanup.CleanupAfterSlicer$CleanupAfterSliceSpec.getCleanupInfo(CleanupAfterSlicer.java:39) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:50) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:12) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:72) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:6) at configurationslicing.ConfigurationSlicing$SliceExecutor.execute(ConfigurationSlicing.java:125) at configurationslicing.ConfigurationSlicing$SliceExecutor.init(ConfigurationSlicing.java:113) at configurationslicing.ConfigurationSlicing.getDynamic(ConfigurationSlicing.java:98) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java Method hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed has been removed from WSCleanup plugin since 0.13: https://github.com/jenkinsci/ws-cleanup-plugin/commit/71ee66716f43d046881de857546654a7beea 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] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
vdupain commented on JENKINS-15934 NPE when trying to open Delete workspace when build is done So same issue for me with plugin ws-cleanup 0.16 and configurationslicing 1.37. Method hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed has been removed from WSCleanup plugin since 0.13: https://github.com/jenkinsci/ws-cleanup-plugin/commit/71ee66716f43d046881de857546654a7beea 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] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
vdupain edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done So same issue for me with plugin ws-cleanup 0.16 and configurationslicing 1.37: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z at configurationslicing.wscleanup.CleanupAfterSlicer$CleanupAfterSliceSpec.getCleanupInfo(CleanupAfterSlicer.java:39) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:50) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:12) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:72) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:6) at configurationslicing.ConfigurationSlicing$SliceExecutor.execute(ConfigurationSlicing.java:125) at configurationslicing.ConfigurationSlicing$SliceExecutor.init(ConfigurationSlicing.java:113) at configurationslicing.ConfigurationSlicing.getDynamic(ConfigurationSlicing.java:98) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java Method hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed has been removed from WSCleanup plugin since 0.13: https://github.com/jenkinsci/ws-cleanup-plugin/commit/71ee66716f43d046881de857546654a7beea 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-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
vdupain commented on JENKINS-9120 RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow Same issue on our jenkins (1.499), the stacktrace: Jan 22, 2013 4:11:23 AM winstone.Logger logInternal WARNING: Untrapped Error in Servlet java.lang.ArrayIndexOutOfBoundsException: -255 at hudson.util.RingBufferLogHandler.publish(RingBufferLogHandler.java:52) at java.util.logging.Logger.log(Logger.java:478) at java.util.logging.Logger.doLog(Logger.java:500) at java.util.logging.Logger.logp(Logger.java:616) at java.util.logging.Logger.entering(Logger.java:872) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:155) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 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
