[JIRA] (JENKINS-61220) plugin version 2.1.0 can not parse output.xml any more

27 views
Skip to first unread message

d.richter@cid.com (JIRA)

unread,
Feb 25, 2020, 7:27:02 AM2/25/20
to jenkinsc...@googlegroups.com
Dirk Richter created an issue
 
Jenkins / Bug JENKINS-61220
plugin version 2.1.0 can not parse output.xml any more
Issue Type: Bug Bug
Assignee: jpiironen
Components: robot-plugin
Created: 2020-02-25 12:26
Environment: windows server 2012 R2, Jenkins ver. 2.204.2
Priority: Blocker Blocker
Reporter: Dirk Richter

i found a regression in version 2.1.0, which can be solved by rollback to version 2.0.1.

D:\Jenkins\workspace\DMM-CID_dev>exit 0 
Robot results publisher started...
-Parsing output xml:
Failed!
java.io.IOException: Parsing of output xml failed!
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:104)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:54)
	at hudson.FilePath.act(FilePath.java:1075)
	at hudson.FilePath.act(FilePath.java:1058)
	at hudson.plugins.robot.RobotParser.parse(RobotParser.java:49)
	at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:221)
	at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:243)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
	at hudson.model.Build$BuildExecution.post2(Build.java:186)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
	at hudson.model.Run.execute(Run.java:1878)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:427)
Caused by: javax.xml.stream.XMLStreamException: Illegal xml input. Could not find end of element status. Unexpected end of element kw (at line: 36 column: 1)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.xmlException(RobotParser.java:179)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.ignoreUntilEnds(RobotParser.java:251)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.processTest(RobotParser.java:313)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:155)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:153)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:153)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.parseResult(RobotParser.java:123)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:99)
	... 16 more
Build step 'Publish Robot Framework test results' changed build result to FAILURE
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

d.richter@cid.com (JIRA)

unread,
Feb 25, 2020, 7:28:02 AM2/25/20
to jenkinsc...@googlegroups.com
Dirk Richter updated an issue
Change By: Dirk Richter
i found a regression in robot-plugin version 2.1.0, which can be solved by rollback to version 2.0.1.

{noformat}
{noformat}

d.richter@cid.com (JIRA)

unread,
Feb 25, 2020, 9:06:03 AM2/25/20
to jenkinsc...@googlegroups.com

d.richter@cid.com (JIRA)

unread,
Feb 26, 2020, 3:35:05 AM2/26/20
to jenkinsc...@googlegroups.com
Dirk Richter updated an issue
Change By: Dirk Richter
Environment: windows server 2012 R2, Jenkins ver. 2.204.2 , robotframework==3.1.2

d.richter@cid.com (JIRA)

unread,
Feb 26, 2020, 3:35:05 AM2/26/20
to jenkinsc...@googlegroups.com

aleksi.simell@eficode.com (JIRA)

unread,
Feb 26, 2020, 3:35:05 AM2/26/20
to jenkinsc...@googlegroups.com
Aleksi Simell assigned an issue to Aleksi Simell
Change By: Aleksi Simell
Assignee: jpiironen Aleksi Simell

aleksi.simell@eficode.com (JIRA)

unread,
Feb 26, 2020, 3:39:02 AM2/26/20
to jenkinsc...@googlegroups.com
Aleksi Simell commented on Bug JENKINS-61220
 
Re: plugin version 2.1.0 can not parse output.xml any more

I'm still trying to reproduce this. According to Robot Framework 3.1 release notes there was a change to output.xml creation, but I would've imagined this issue had risen already back then.

d.richter@cid.com (JIRA)

unread,
Feb 26, 2020, 3:43:06 AM2/26/20
to jenkinsc...@googlegroups.com

i'm not sure if the reason is a change in robotframework, because rollback to robot-plugin 2.0.1 works perfect (output.xml can be parsed then)

aleksi.simell@eficode.com (JIRA)

unread,
Feb 26, 2020, 3:45:03 AM2/26/20
to jenkinsc...@googlegroups.com

Don't know, but I still need an output.xml file which the plugin cannot parse

d.richter@cid.com (JIRA)

unread,
Feb 26, 2020, 5:00:07 AM2/26/20
to jenkinsc...@googlegroups.com

more analysis showed, that on this point a kw starts with an embedded stacktrace, maybe this is the reason:

<kw name="Get In Run" library="Configuration">
<doc>Gets the value of the shared run-variable named *key*</doc>
<arguments>
<arg>DMMVersion</arg>
<arg>default=${EMPTY}</arg>
</arguments>
<assign>
<var>${v}</var>
</assign>
<msg timestamp="20200226 10:47:44.557" level="TRACE">Arguments: [ 'DMMVersion' | default='' ]</msg>
<msg timestamp="20200226 10:47:44.557" level="INFO">GetInRun D:\CID.Artemis\Files\NTA\Robot\temp/200226runShare_dev62.yaml@DMMVersion =&gt;  ... 
GetRunShare D:\CID.Artemis\Files\NTA\Robot\temp/200226runShare_dev62.yaml
Traceback (most recent call last):
  File "D:\CID.Artemis\Files\NTA\Robot\Lib\Configuration.py", line 76, in GetRunShare
    with open(self.runShareFile, 'r', encoding='UTF-8') as stream:
FileNotFoundError: [Errno 2] No such file or directory: 'D:\\CID.Artemis\\Files\\NTA\\Robot\\temp/200226runShare_dev62.yaml'
   =&gt; {}
GetInRun D:\CID.Artemis\Files\NTA\Robot\temp/200226runShare_dev62.yaml@DMMVersion =&gt;</msg>
<msg timestamp="20200226 10:47:44.557" level="TRACE">Return: ''</msg>
<msg timestamp="20200226 10:47:44.557" level="INFO">${v} = </msg>
<status status="PASS" starttime="20200226 10:47:44.557" endtime="20200226 10:47:44.557"></status>
</kw>

i'll try to create a micro-demo sample for this...

aleksi.simell@eficode.com (JIRA)

unread,
Feb 26, 2020, 5:02:02 AM2/26/20
to jenkinsc...@googlegroups.com
Aleksi Simell started work on Bug JENKINS-61220
 
Change By: Aleksi Simell
Status: Open In Progress

aleksi.simell@eficode.com (JIRA)

unread,
Feb 26, 2020, 5:02:03 AM2/26/20
to jenkinsc...@googlegroups.com

My colleague also reproduced this and he provided me with his output.xml and I was able to reproduce this as well. I'm investigating this.

aleksi.simell@eficode.com (JIRA)

unread,
Feb 26, 2020, 6:53:02 AM2/26/20
to jenkinsc...@googlegroups.com

aleksi.simell@eficode.com (JIRA)

unread,
Feb 27, 2020, 1:21:03 AM2/27/20
to jenkinsc...@googlegroups.com
Change By: Aleksi Simell
Status: In Progress Review
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

aleksi.simell@eficode.com (JIRA)

unread,
Feb 27, 2020, 1:32:03 AM2/27/20
to jenkinsc...@googlegroups.com
Change By: Aleksi Simell
Status: In Review Fixed but Unreleased
Resolution: Fixed

aleksi.simell@eficode.com (JIRA)

unread,
Feb 27, 2020, 1:41:03 AM2/27/20
to jenkinsc...@googlegroups.com
 

Fix released as 2.1.1 (will be available in update-center in several hours).

Change By: Aleksi Simell
Status: Fixed but Unreleased Resolved
Released As: 2.1.1
Reply all
Reply to author
Forward
0 new messages