• Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Critical Critical
    • robot-plugin
    • Robot Framework Jenkins Plugin version: 3.0.1
      Robot Framework version: 3.0.4

      An error occurs using the current last version of Jenkins Robot Plugin (3.0.1):

       15:32:46 -Parsing output xml:[Pipeline] }[Pipeline] // scriptError when executing always post condition:
       Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to win10bis.inpeco.com
       at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1800)
       at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
       at hudson.remoting.Channel.call(Channel.java:1001)
       at hudson.FilePath.act(FilePath.java:1158)
       at hudson.FilePath.act(FilePath.java:1147)
       at hudson.plugins.robot.RobotParser.parse(RobotParser.java:48)
       at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:245)
       at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:267)
       at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
       at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
       at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
       at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
       at java.lang.Thread.run(Thread.java:748)
       java.lang.IllegalStateException: Not a textual event (END_ELEMENT)
       at com.ctc.wstx.sr.BasicStreamReader.throwNotTextual(BasicStreamReader.java:5478)
       at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:806)
       at hudson.plugins.robot.RobotParser$RobotParserCallable.processArgs(RobotParser.java:474)
       at hudson.plugins.robot.RobotParser$RobotParserCallable.processKeyword(RobotParser.java:440)
       at hudson.plugins.robot.RobotParser$RobotParserCallable.processKeyword(RobotParser.java:446)
       at hudson.plugins.robot.RobotParser$RobotParserCallable.processTest(RobotParser.java:295)
       at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:153)
       at hudson.plugins.robot.RobotParser$RobotParserCallable.parseResult(RobotParser.java:121)
       at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:97)
       at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:52)
       at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3314)
       at hudson.remoting.UserRequest.perform(UserRequest.java:211)
       at hudson.remoting.UserRequest.perform(UserRequest.java:54)
       at hudson.remoting.Request$2.run(Request.java:376)
       at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
       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.lambda$newThread$0(Engine.java:119)
       at java.lang.Thread.run(Unknown Source)

      Issue can be due to refactoring applied to properly parse arguments and args?

      Attached 'affected' output.xml file.

          [JENKINS-66150] Issue on output.xml parser

          Aleksi Simell added a comment - - edited

          Hi iandam,

          I created a unit test with your output.xml parser and it passed just fine. However, when I searched for a specific line in your stack trace (org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)) I found this, which suggests this might be caused by running steps in parallel.

          What does your job look like? Do you have parallel stages triggering the plugin at the same time?

          Aleksi Simell added a comment - - edited Hi iandam , I created a unit test with your output.xml parser and it passed just fine. However, when I searched for a specific line in your stack trace (org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)) I found this , which suggests this might be caused by running steps in parallel. What does your job look like? Do you have parallel stages triggering the plugin at the same time?

          Aleksi Simell added a comment -

          Closing due to lack of info.

          Aleksi Simell added a comment - Closing due to lack of info.

            aleksisimell Aleksi Simell
            iandam Damiano
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: