[JIRA] (JENKINS-50524) robotframework plugin throws exception on parsing output.xml

4 views
Skip to first unread message

xiaochenz@gmail.com (JIRA)

unread,
Apr 2, 2018, 4:34:02 PM4/2/18
to jenkinsc...@googlegroups.com
Jessica Zhang created an issue
 
Jenkins / Bug JENKINS-50524
robotframework plugin throws exception on parsing output.xml
Issue Type: Bug Bug
Assignee: jpiironen
Components: robot-plugin
Created: 2018-04-02 20:33
Priority: Major Major
Reporter: Jessica Zhang

When a build fails, pybot will never be called because it's not necessary since the build failed. Because of this, there isn't a need to process robotframework reports since the output directory will never exist. So the idea is to not do anything upon a build failure.

Here is the unnecessary exception:
Robot results publisher started...
-Parsing output xml:
Failed!
/var/lib/jenkins/jobs/XXXXX/workspace/my_robot_results does not exist.
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:483)
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:460)
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:65)
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:51)
at hudson.FilePath.act(FilePath.java:920)
at hudson.FilePath.act(FilePath.java:893)
at hudson.plugins.robot.RobotParser.parse(RobotParser.java:46)
at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:218)
at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:241)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:709)
at hudson.model.Build$BuildExecution.post2(Build.java:182)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:658)
at hudson.model.Run.execute(Run.java:1734)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Build step 'Publish Robot Framework test results' changed build result to FAILURE
Finished: FAILURE

It would be great to have an option to mark the build as failed or success whether or not the output_dir exists... So a check box in settings that says something along the lines of....
"Don't mark build as failed if output_dir doesn't exist.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

xiaochenz@gmail.com (JIRA)

unread,
Apr 2, 2018, 4:39:02 PM4/2/18
to jenkinsc...@googlegroups.com
Jessica Zhang assigned an issue to Unassigned
 

After seeing the output parsing exception, I tried running command "rebot output.xml". The log.html and report.html looked fine. Due to this exception, Robot results/test summary are not shown on Jenkins. Could this exception be handled more gracefully?

Change By: Jessica Zhang
Assignee: jpiironen

xiaochenz@gmail.com (JIRA)

unread,
Apr 2, 2018, 4:40:02 PM4/2/18
to jenkinsc...@googlegroups.com
Jessica Zhang edited a comment on Bug JENKINS-50524
 
Re: robotframework plugin throws exception on parsing output.xml
After seeing the output parsing exception, I tried running command "rebot output.xml". The  Both log.html and report.html files generated looked fine. Due I am not sure why this exception is thrown.

What makes matter worse is that, due
to this exception, Robot results/test summary are not shown on Jenkins. Could this exception be handled more gracefully?

xiaochenz@gmail.com (JIRA)

unread,
Apr 2, 2018, 4:54:01 PM4/2/18
to jenkinsc...@googlegroups.com
Jessica Zhang edited a comment on Bug JENKINS-50524
After seeing Despite the output parsing exception, log and report html files generated from the build looked normal. I tried running also manually ran command "rebot output.xml". Both log.html and report.html files generated after running the command looked fine as well . I am not sure why this exception is thrown.

What makes matter worse is that, due to this exception, Robot results/test summary are not
published or shown on Jenkins build page . Could this exception be handled more gracefully?

jpiironen@java.net (JIRA)

unread,
Aug 7, 2018, 5:21:01 AM8/7/18
to jenkinsc...@googlegroups.com

Hi,

Is this issue still relevant for you? It seems that the xml is somehow corrupt in a way that robot's parser library can handle, but the stax parser used by the plugin can not.

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

aleksi.simell@eficode.com (JIRA)

unread,
Jan 17, 2020, 1:00:03 AM1/17/20
to jenkinsc...@googlegroups.com
Aleksi Simell closed an issue as Won't Fix
 

Closing due to lack of input. Please re-open if still an issue.

Change By: Aleksi Simell
Status: Open Closed
Resolution: Won't Fix
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages