[JIRA] (JENKINS-40869) Allow for unescaped XML in test detail output
Title: Message Title Tim Drury created an issue Jenkins / JENKINS-40869 Allow for unescaped XML in test detail output Issue Type: New Feature Assignee: Unassigned Attachments: 2017-01-06_15-13-22.png Components: junit-plugin Created: 2017/Jan/06 8:18 PM Environment: Jenkins 1.596.1 junit-plugin 1.8 on SUSE Linux Priority: Major Reporter: Tim Drury We run SoapUI integration tests in a jenkins job. SoapUI creates the test results in junit XML format. The details of each test includes the XML request and response SoapUI. In Jenkins, when expanding a test element in the UI, the details are shown with the XML escaped making it very hard to quickly identify issues. I've attached a screenshot as an example I'm ok with the escaping of the html which can be seen near the top, but the escaping of the '<' and '>' and single quotes makes the XML very difficult to follow. Is it possible to add an option to NOT escape the XML special characters (<,>,')?
[JIRA] [maven-plugin] (JENKINS-4152) Incremental builds should include previous builds' modules if previous build failed
Tim Drury commented on JENKINS-4152 Incremental builds should include previous builds modules if previous build failed I see this behavior happening in Jenkins 1.596.1. A job is configured for incremental build. Module A fails due to a broken unit test. A change to module B is made. The next build builds only module B so the build goes green even though module A's unit test is still broken. Unstable and failed modules should be included in the next incremental build (and subsequent builds until the module is stable). 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] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Tim Drury commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand We just started getting this issue with on one job which had been running fine. I don't think there have been any system configuration changes. We're on 1.532.1 on Windows Server 2008 R2. Jenkins is run with JDK 1.6.0_26 (x64). I found this in the Jenkins error log: Apr 2, 2014 3:02:48 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job me-main-coverage-test java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:470) at java.lang.Integer.parseInt(Integer.java:499) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:87) at hudson.model.Job.getLastSuccessfulBuild(Job.java:833) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:185) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:746) at hudson.maven.MavenModule.updateTransientActions(MavenModule.java:485) at hudson.model.AbstractProject.onLoad(AbstractProject.java:333) at hudson.maven.MavenModule.onLoad(MavenModule.java:283) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:761) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$18.run(Jenkins.java:2562) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) 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) Apr 2, 2014 3:06:06 PM jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs I verified all the job/builds/last* files are all correct. lastSuccessfulBuild contains 792 and the 792 symlink and target directory look ok: 04/01/2014 04:29 PMDIR 2014-04-01_13-51-33 ... 04/01/2014 01:51 PMSYMLINKD 792 2014-04-01_13-51-33 ... I can go into 792, but not any of the linked folders within: D:\Jenkins\instance\jobs\me-main-coverage-test\buildscd 792 D:\Jenkins\instance\jobs\me-main-coverage-test\builds\792cd com.sap.mfg.me$me The filename, directory name, or volume label syntax is incorrect. 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] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Tim Drury commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Mine says the Maven Integration Plugin is version 2.0.3. 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] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Tim Drury commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand we use -XX:MaxPermSize=400m so that's probably not it. 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] [disk-usage] (JENKINS-20876) disk usage hangs http request to view job
Tim Drury commented on JENKINS-20876 disk usage hangs http request to view job Thanks, Lucie. I'm pretty confident this issue is caused by this one: https://issues.jenkins-ci.org/browse/JENKINS-19544 - if you can't reproduce this on 1.542, then feel free to close it (or mark as caused by 19544). 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] [disk-usage] (JENKINS-20876) disk usage hangs http request to view job
Tim Drury commented on JENKINS-20876 disk usage hangs http request to view job After further OOM errors even after disk-usage has been disabled, I think the issue is with core Jenkins. See this thread on the user list: https://groups.google.com/d/msg/jenkinsci-users/ZK1J6R2ej4I/SF1giBkUugYJ 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] [disk-usage] (JENKINS-20876) disk usage hangs http request to view job
Tim Drury created JENKINS-20876 disk usage hangs http request to view job Issue Type: Bug Affects Versions: current Assignee: Lucie Votypkova Components: disk-usage Created: 04/Dec/13 8:39 PM Description: after upgrading to the latest jenkins and plugins, when someone tries to fetch the page for a particularly large job, the request hangs and the thread is stuck. Disabling the disk-usage plugin fixed the issue and now the job can be viewed. Here is the thread dump for the thread: "Handling GET /job/me-main/ : RequestHandlerThread12" daemon prio=5 RUNNABLE java.util.WeakHashMap.eq(WeakHashMap.java:259) java.util.WeakHashMap.get(WeakHashMap.java:353) com.thoughtworks.xstream.core.util.WeakCache.get(WeakCache.java:57) java.util.Collections$SynchronizedMap.get(Collections.java:1975) com.thoughtworks.xstream.converters.basic.StringConverter.fromString(StringConverter.java:89) com.thoughtworks.xstream.converters.SingleValueConverterWrapper.fromString(SingleValueConverterWrapper.java:41) com.thoughtworks.xstream.converters.SingleValueConverterWrapper.unmarshal(SingleValueConverterWrapper.java:49) com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) com.thoughtworks.xstream.converters.collections.MapConverter.putCurrentEntryIntoMap(MapConverter.java:86) com.thoughtworks.xstream.converters.collections.MapConverter.populateMap(MapConverter.java:78) com.thoughtworks.xstream.converters.collections.MapConverter.populateMap(MapConverter.java:72) com.thoughtworks.xstream.converters.collections.MapConverter.unmarshal(MapConverter.java:67) hudson.util.PackedMap$ConverterImpl.unmarshal(PackedMap.java:175) hudson.util.XStream2$AssociatedConverterImpl.unmarshal(XStream2.java:338) com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222)
[JIRA] [disk-usage] (JENKINS-20876) disk usage hangs http request to view job
Tim Drury commented on JENKINS-20876 disk usage hangs http request to view job A similar issue recommended increasing heap and permgen which I did from 3G to 4.2G (heap) and 512M to 1G (permgen), but the problem still occurred. I let the page try to load for 4 hours and CPU on all 4 cores was 90%+. 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-13332) OutOfMemoryError from Perforce polling
[ https://issues.jenkins-ci.org/browse/JENKINS-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161646#comment-161646 ] Tim Drury commented on JENKINS-13332: - it has not occurred again OutOfMemoryError from Perforce polling -- Key: JENKINS-13332 URL: https://issues.jenkins-ci.org/browse/JENKINS-13332 Project: Jenkins Issue Type: Bug Components: perforce Affects Versions: current Environment: Windows Server 2008, Jenkins 1.450, Perforce plugin 1.3.7, Jenkins JVM 1.6.0_26 64-bit -Xmx=1280mb (at time of crash - it's been increased); 1 master, 2 slaves, all SCM polling on master; See attached jenkins-info.txt Reporter: Tim Drury Labels: outofmemoryerror, perforce, scm Attachments: jenkins-info.txt Our QA noticed no new builds for 2 days. When I checked the polling log of one project it was: Perforce Polling Log Started on Apr 1, 2012 7:00:38 PM Looking for changes... Using master Using master perforce client: jenkins_me-main ERROR: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space I did not follow the Jenkins wiki process :(. If this happens again, I'll use it to get more information. Here is the stack trace: Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:78) at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:66) at hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1323) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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) We do keep Jenkins running without periodic reboots so I'm thinking there may be a memory leak somewhere as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13109) Huge changelogs eat all the Java memory
[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161153#comment-161153
]
Tim Drury commented on JENKINS-13109:
-
I noticed the same error today on 1.450 w/ perforce plugin 1.3.7. In my case,
it isn't caused by huge changelogs - at least that I can tell. We don't have
huge changelogs. We do have 2 slaves and all polling is done on the master.
Here is the stack trace:
Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling
SEVERE: Failed to record SCM polling
java.lang.OutOfMemoryError: Java heap space
at
hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:78)
at
hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:66)
at
hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54)
at
hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208)
at
hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject.poll(AbstractProject.java:1323)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
at
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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)
We do keep Jenkins running without period reboots so I'm thinking there may be
a memory leak somewhere as well. If anyone can give me hints how to get more
information, I'll try to provide it.
-tim
Huge changelogs eat all the Java memory
---
Key: JENKINS-13109
URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
Project: Jenkins
Issue Type: Bug
Components: perforce
Environment: Windows Server 2008 HPC Edition
64-bit JVM 1.6.0_29
Running Jenkins service with arguments-Xrs -Xmx2048m
-Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar
%BASE%\jenkins.war --httpPort=8080/arguments
Reporter: Mikko Tapaninen
With really huge changelists the p4 plugin can run out of java heap space. At
least it looks like the reason for memory problems would be huge
changelog.xml files. An example case:
- a changelist with 40 files
- results in a changelog.xml size 110MB
- Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
Maybe there should be an option to limit the amount of files that p4 plugin
reads to from changelists?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13109) Huge changelogs eat all the Java memory
[ https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161153#comment-161153 ] Tim Drury edited comment on JENKINS-13109 at 4/3/12 2:41 PM: - I noticed the same error today on 1.450 w/ perforce plugin 1.3.7. In my case, it isn't caused by huge changelogs - at least that I can tell. We don't have huge changelogs. We do have 2 slaves and all polling is done on the master. Here is the stack trace: Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:78) at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:66) at hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1323) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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) We do keep Jenkins running without periodic reboots so I'm thinking there may be a memory leak somewhere as well. If anyone can give me hints how to get more information, I'll try to provide it. -tim was (Author: timdrury): I noticed the same error today on 1.450 w/ perforce plugin 1.3.7. In my case, it isn't caused by huge changelogs - at least that I can tell. We don't have huge changelogs. We do have 2 slaves and all polling is done on the master. Here is the stack trace: Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:78) at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:66) at hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1323) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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) We do keep Jenkins running without period reboots so I'm thinking there may be a memory leak somewhere as well. If anyone can give me hints how to get more information, I'll try to provide it. -tim Huge changelogs eat all the Java memory
[JIRA] (JENKINS-13332) OutOfMemoryError from Perforce polling
[ https://issues.jenkins-ci.org/browse/JENKINS-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161181#comment-161181 ] Tim Drury commented on JENKINS-13332: - This issue started out here: https://issues.jenkins-ci.org/browse/JENKINS-13109 but Rob identified it as a separate issue so I created this Jira issue. OutOfMemoryError from Perforce polling -- Key: JENKINS-13332 URL: https://issues.jenkins-ci.org/browse/JENKINS-13332 Project: Jenkins Issue Type: Bug Components: perforce Affects Versions: current Environment: Windows Server 2008, Jenkins 1.450, Perforce plugin 1.3.7, Jenkins JVM 1.6.0_26 64-bit -Xmx=1280mb (at time of crash - it's been increased); 1 master, 2 slaves, all SCM polling on master; See attached jenkins-info.txt Reporter: Tim Drury Labels: outofmemoryerror, perforce, scm Attachments: jenkins-info.txt Our QA noticed no new builds for 2 days. When I checked the polling log of one project it was: Perforce Polling Log Started on Apr 1, 2012 7:00:38 PM Looking for changes... Using master Using master perforce client: jenkins_me-main ERROR: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space I did not follow the Jenkins wiki process :(. If this happens again, I'll use it to get more information. Here is the stack trace: Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:78) at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:66) at hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1323) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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) We do keep Jenkins running without periodic reboots so I'm thinking there may be a memory leak somewhere as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13332) OutOfMemoryError from Perforce polling
Tim Drury created JENKINS-13332: --- Summary: OutOfMemoryError from Perforce polling Key: JENKINS-13332 URL: https://issues.jenkins-ci.org/browse/JENKINS-13332 Project: Jenkins Issue Type: Bug Components: perforce Affects Versions: current Environment: Windows Server 2008, Jenkins 1.450, Perforce plugin 1.3.7, Jenkins JVM 1.6.0_26 64-bit -Xmx=1280mb (at time of crash - it's been increased); 1 master, 2 slaves, all SCM polling on master; See attached jenkins-info.txt Reporter: Tim Drury Attachments: jenkins-info.txt Our QA noticed no new builds for 2 days. When I checked the polling log of one project it was: Perforce Polling Log Started on Apr 1, 2012 7:00:38 PM Looking for changes... Using master Using master perforce client: jenkins_me-main ERROR: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space I did not follow the Jenkins wiki process :(. If this happens again, I'll use it to get more information. Here is the stack trace: Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:78) at hudson.remoting.FastPipedInputStream.init(FastPipedInputStream.java:66) at hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1323) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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) We do keep Jenkins running without periodic reboots so I'm thinking there may be a memory leak somewhere as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13109) Huge changelogs eat all the Java memory
[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161180#comment-161180
]
Tim Drury edited comment on JENKINS-13109 at 4/3/12 6:59 PM:
-
Ok, I'll move my stack trace to a new issue and I'll update with OOM Error info
when/if it occurs again. Thanks again, Rob.
Created this issue: https://issues.jenkins-ci.org/browse/JENKINS-13332
was (Author: timdrury):
Ok, I'll move my stack trace to a new issue and I'll update with OOM Error
info when/if it occurs again. Thanks again, Rob.
Huge changelogs eat all the Java memory
---
Key: JENKINS-13109
URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
Project: Jenkins
Issue Type: Bug
Components: perforce
Environment: Windows Server 2008 HPC Edition
64-bit JVM 1.6.0_29
Running Jenkins service with arguments-Xrs -Xmx2048m
-Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar
%BASE%\jenkins.war --httpPort=8080/arguments
Reporter: Mikko Tapaninen
With really huge changelists the p4 plugin can run out of java heap space. At
least it looks like the reason for memory problems would be huge
changelog.xml files. An example case:
- a changelist with 40 files
- results in a changelog.xml size 110MB
- Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
Maybe there should be an option to limit the amount of files that p4 plugin
reads to from changelists?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10333) Maven jobs don't report all details of failures
[
https://issues.jenkins-ci.org/browse/JENKINS-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158815#comment-158815
]
Tim Drury commented on JENKINS-10333:
-
I get the same error on Jenkins 1.450 compiling a maven 3.0.4 project. This
_just_ started happening on our Jenkins system and it correlates to our move
from maven 2.2.1 to maven 3.0.4, but I could swear we got good compilation
error messages even with 3.0.4. The compiler plugin is 2.0.2.
Maven jobs don't report all details of failures
---
Key: JENKINS-10333
URL: https://issues.jenkins-ci.org/browse/JENKINS-10333
Project: Jenkins
Issue Type: Bug
Components: maven2
Environment: Jenkins 1.420 but I'm almost sure to have see it before
Reporter: Arnaud Héritier
Priority: Critical
I have a maven build which is failing because of compilation error.
My local Maven (3.0.3) build returns this :
{code}
[INFO]
[INFO] Building eXo Social Portlet Web App 1.2.1-SNAPSHOT
[INFO]
Downloading:
http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.exoplatform.org/private/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
Downloaded:
http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
(2 KB at 0.0 KB/sec)
Downloading:
http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.pom
Downloaded:
http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.pom
(3 KB at 4.2 KB/sec)
Downloading:
http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.jar
Downloaded:
http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.jar
(35 KB at 52.6 KB/sec)
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @
exo.social.webapp.portlet ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-plugin-versions)
@ exo.social.webapp.portlet ---
[WARNING] This rule is not compatible with the current version of Maven. The
rule is not able to perform any checks.
[INFO]
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-java-version) @
exo.social.webapp.portlet ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-maven-version) @
exo.social.webapp.portlet ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.1:resources (default-resources) @
exo.social.webapp.portlet ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @
exo.social.webapp.portlet ---
[INFO] Compiling 28 source files to
/Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/target/classes
[INFO]
[INFO] Reactor Summary:
[INFO]
..
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3:58.991s
[INFO] Finished at: Thu Jul 14 14:30:36 CEST 2011
[INFO] Final Memory: 25M/125M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project exo.social.webapp.portlet: Compilation failure:
Compilation failure:
[ERROR]
/Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UIHomeSpacePortlet.java:[64,36]
[deprecation]
hasEditPermission(org.exoplatform.social.core.space.model.Space,java.lang.String)
in org.exoplatform.social.core.space.spi.SpaceService has been deprecated
[ERROR]
[ERROR]
/Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UISocialLogoPortlet.java:[104,13]
[deprecation] getOrCreateIdentity(java.lang.String,java.lang.String) in
org.exoplatform.social.core.manager.IdentityManager has been deprecated
[ERROR]
[ERROR]
