[JIRA] [robot-plugin] (JENKINS-18675) Failure in suite teardown does not fail test cases
Kevin Ormbrek created JENKINS-18675 Failure in suite teardown does not fail test cases Issue Type: Bug Affects Versions: current Assignee: jpiironen Components: robot-plugin Created: 09/Jul/13 2:21 PM Description: When generating the report and log files from the output file, Robot Framework marks all tests failed if the suite teardown failed. The Jenkins plugin does not do the same. Project: Jenkins Priority: Major Reporter: Kevin Ormbrek 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] [robot-plugin] (JENKINS-9386) Links to local screenshots in Robot plugin don't work if I view logs from "Original report files"
Kevin Ormbrek commented on JENKINS-9386 Links to local screenshots in Robot plugin don't work if I view logs from "Original report files" This is resolved in 1.2.1 with the Other files to copy option. For Selenium2Library, value */.png for Other files to copy would archive screenshots in the Robot Framework results and make the log contain proper screenshots. 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] [file-leak-detector] (JENKINS-18180) File Leak Detector Plugin does not work if JENKINS_HOME has a space in it
Kevin Ormbrek updated JENKINS-18180 File Leak Detector Plugin does not work if JENKINS_HOME has a space in it Change By: Kevin Ormbrek (03/Jun/13 8:20 PM) Attachment: StackTrace.txt Description: Exception in thread "main" com.sun.tools.attach.AgentLoadException: Agent JAR not found or no Agent-Class attributeIn the stack trace you can see in the path to the file leak detector jar, the space is being "percent-encoded" e.g. C:\Program%20Files\Jenkins...Moving the Jenkins folder so that JENKINS_HOME did not have a space in it resolved the issue. Response (stack trace) when attempting to activate the file leak detector is attached. 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] [file-leak-detector] (JENKINS-18180) File Leak Detector Plugin does not work if JENKINS_HOME has a space in it
Kevin Ormbrek created JENKINS-18180 File Leak Detector Plugin does not work if JENKINS_HOME has a space in it Issue Type: Bug Assignee: Unassigned Components: file-leak-detector Created: 03/Jun/13 6:47 PM Description: Exception in thread "main" com.sun.tools.attach.AgentLoadException: Agent JAR not found or no Agent-Class attribute In the stack trace you can see in the path to the file leak detector jar, the space is being "percent-encoded" e.g. C:\Program%20Files\Jenkins... Moving the Jenkins folder so that JENKINS_HOME did not have a space in it resolved the issue. Project: Jenkins Priority: Minor Reporter: Kevin Ormbrek 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-17328) output.xml kept open after build if parsing error occurs causing subsequent runs to fail
Kevin Ormbrek
created JENKINS-17328
output.xml kept open after build if parsing error occurs causing subsequent runs to fail
Issue Type:
Bug
Assignee:
jpiironen
Components:
robot-plugin
Created:
22/Mar/13 5:54 PM
Description:
Steps to reproduce:
Have an output.xml file with broken XML when the plugin processes the results.
After the job fails, try to delete the output.xml file.
Expected:
Can delete the file.
Actual:
File in use, cannot be deleted. The JVM's process keeps the file open. This causes subsequent job runs to fail until the slave agent is restarted to release the file.
Stack trace from when the file is opened and not closed:
hudson.util.IOException2: remote file operation failed: C:\Jenkins\workspace\Apollo_SKU_IT\test-output at hudson.remoting.Channel@c591b4:Robot-2
at hudson.FilePath.act(FilePath.java:861)
at hudson.FilePath.act(FilePath.java:838)
at hudson.plugins.robot.RobotParser.parse(RobotParser.java:45)
at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:239)
at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:261)
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: hudson.remoting.ProxyException: java.io.IOException: Parsing of output xml failed!
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:90)
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:50)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
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(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:58)
at java.lang.Thread.run(Unknown Source)
Caused by: hudson.remoting.ProxyException: com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block in end tag
at [row,col {unknown-source}]: [1649,61]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOB(StreamScanner.java:700)
at com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1054)
at com.ctc.wstx.sr.StreamScanner.getNextCharFromCurrent(StreamScanner.java:811)
at com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3206)
at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2832)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
at hudson.plugins.robot.RobotParser$RobotParserCallable.processTest(RobotParser.java:190)
at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:158)
at hudson.plugins.robot.RobotParser$RobotParserCallable.parseResult(RobotParser.java:114)
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:88)
... 12 more
Environment:
Jenkins 1.505 (job running on a slave that has Java 1.6.0_30-b12 on Windows Server 2003 32-bit), Robot Framework Plugin 1.2.3
Project:
Jenkins
Priority:
[JIRA] (JENKINS-16525) Python plugin: use fixed-width font
Kevin Ormbrek created JENKINS-16525 Python plugin: use fixed-width font Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: python Created: 29/Jan/13 6:31 PM Description: I submitted a pull request for this Project: Jenkins Labels: plugin Priority: Trivial Reporter: Kevin Ormbrek 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.
