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

TestNG plugin is unable to parse << in results xml

    Details

    • Similar Issues:

      Description

      The following part of testng-results.xml makes testng plugin to fail parsing:

        <exception class="org.testng.SkipException">
          <message>
                    <![CDATA[Incremental refresh does not support dst param filters. Error message <<Lines differ. Actual: [[[first value] Memo_M_1  *multiple*dst*param*filter*, 9138653185713543795, 1, ABXFwWAAEAANjKpAAa], [[second value][line 1] Memo_M_1 RDBL Test object create/delete in one replication
      [line 2] Memo_M_1 RDBL Test object create/delete in one replication, 9138653185713543795, 2, ABXFwWAAEAANjKpABC]]. Expected: [[[first value] Memo_M_1  *multiple*dst*param*filter*, 9138653185713543795, 1, MACRO(#$NOT_NULL$#)]]: lists don't have the same size expected [1] but found [2]>> matches exclude regexp <<Lines differ. Actual: [[[first value] Memo_M_1  *multiple*dst*param*filter*, 9138653185713543795, 1, \[\^]\]\+], [[second value][line 1] Memo_M_1 RDBL Test object create/delete in one replication
      [line 2] Memo_M_1 RDBL Test object create/delete in one replication, 9138653185713543795, 2, \[\^]\]\+]]. Expected: [[[first value] Memo_M_1  *multiple*dst*param*filter*, 9138653185713543795, 1, MACRO(#$NOT_NULL$#)]]: lists don't have the same size expected [1] but found [2]>>]]>
                  </message>
      ...
      

      The message is as follows:

      00:34:42.839 Failed to parse XML: unexpected character in markup < (position: TEXT seen ...e same size expected [1] but found [2]>> matches exclude regexp <<... @175:313) 
      00:34:42.839 org.xmlpull.v1.XmlPullParserException: unexpected character in markup < (position: TEXT seen ...e same size expected [1] but found [2]>> matches exclude regexp <<... @175:313) 
      00:34:42.839 	at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1261)
      00:34:42.839 	at org.xmlpull.mxp1.MXParser.nextToken(MXParser.java:1100)
      00:34:42.839 	at hudson.plugins.testng.parser.ResultsParser.parse(ResultsParser.java:154)
      00:34:42.839 	at hudson.plugins.testng.TestNGTestResultBuildAction.loadResults(TestNGTestResultBuildAction.java:120)
      00:34:42.839 	at hudson.plugins.testng.Publisher.perform(Publisher.java:126)
      00:34:42.839 	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      00:34:42.839 	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
      00:34:42.839 	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)
      00:34:42.839 	at hudson.model.Build$BuildExecution.post2(Build.java:185)
      00:34:42.839 	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)
      00:34:42.839 	at hudson.model.Run.execute(Run.java:1766)
      00:34:42.839 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      00:34:42.839 	at hudson.model.ResourceController.execute(ResourceController.java:98)
      00:34:42.839 	at hudson.model.Executor.run(Executor.java:381)
      

      What if tesngplugin switches to JDK's default parser?\

      Impact: "TestNG Results" link is missing.

        Attachments

          Activity

          Hide
          nullin Nalin Makar added a comment -
          What if tesngplugin switches to JDK's default parser?
          

          A lot of work. Pull requests welcome!

          Show
          nullin Nalin Makar added a comment - What if tesngplugin switches to JDK's default parser? A lot of work. Pull requests welcome!
          Hide
          nullin Nalin Makar added a comment -

          No plans on replacing the XML parser we use currently.

          Show
          nullin Nalin Makar added a comment - No plans on replacing the XML parser we use currently.

            People

            • Assignee:
              nullin Nalin Makar
              Reporter:
              vladimirsitnikov Vladimir Sitnikov
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: