Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-50524

robotframework plugin throws exception on parsing output.xml

    Details

    • Similar Issues:

      Description

      Kentico » Kentico-Windows #59 Console [Jenkins]
      -Parsing output xml:
      Failed!
      java.io.IOException: remote file operation failed: C:\Jenkins\workspace\Kentico\Kentico-Windows\Kentico\REGRESSION\results at hudson.remoting.Channel@a19d0c:JNLP4-connect connection from ecoautomate02.eig.ecogrp.ca/10.1.170.53:1179: hudson.remoting.ProxyException: java.io.IOException: Parsing of output xml failed!
      at hudson.FilePath.act(FilePath.java:992)
      at hudson.FilePath.act(FilePath.java:974)
      at hudson.plugins.robot.RobotParser.parse(RobotParser.java:49)
      at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:217)
      at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:239)
      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:779)
      at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
      at hudson.model.Build$BuildExecution.post2(Build.java:185)
      at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
      at hudson.model.Run.execute(Run.java:1754)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:404)
      Caused by: hudson.remoting.ProxyException: java.io.IOException: Parsing of output xml failed!
      at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:103)
      at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:54)
      at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731)
      at hudson.remoting.UserRequest.perform(UserRequest.java:153)
      at hudson.remoting.UserRequest.perform(UserRequest.java:50)
      at hudson.remoting.Request$2.run(Request.java:336)
      at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
      at java.util.concurrent.FutureTask.run(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at hudson.remoting.Engine$1$1.run(Engine.java:94)
      at java.lang.Thread.run(Unknown Source)
      at ......remote call to JNLP4-connect connection from ecoautomate02.eig.ecogrp.ca/10.1.170.53:1179(Native Method)
      at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
      at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
      at hudson.remoting.Channel.call(Channel.java:822)
      at hudson.FilePath.act(FilePath.java:985)
      ... 14 more
      Caused by: hudson.remoting.ProxyException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF; was expecting a close tag for element <status>
      at [row,col \{unknown-source}]: [1471,88]
      at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:686)
      at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2730)
      at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
      at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:142)
      at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:146)
      at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:146)
      at hudson.plugins.robot.RobotParser$RobotParserCallable.parseResult(RobotParser.java:122)
      at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:98)
      at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:54)
      at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731)
      at hudson.remoting.UserRequest.perform(UserRequest.java:153)
      at hudson.remoting.UserRequest.perform(UserRequest.java:50)
      at hudson.remoting.Request$2.run(Request.java:336)
      at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
      at java.util.concurrent.FutureTask.run(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at hudson.remoting.Engine$1$1.run(Engine.java:94)
      at java.lang.Thread.run(Unknown Source)
      Finished: FAILURE

        Attachments

          Activity

          Hide
          minihunter97 Jessica Zhang added a comment - - edited

          Despite the parsing exception, log and report html files generated from the build looked normal. I 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?

          Show
          minihunter97 Jessica Zhang added a comment - - edited Despite the parsing exception, log and report html files generated from the build looked normal. I 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?
          Hide
          jpiironen jpiironen added a comment -

          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.

          Show
          jpiironen jpiironen added a comment - 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.

            People

            • Assignee:
              Unassigned
              Reporter:
              minihunter97 Jessica Zhang
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: