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

TAP Plugin 2.0.1 fails to parse TAP stream

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: tap-plugin
    • Labels:
      None
    • Environment:
      Jenkins version: 2.7.3; TAP Plugin version 2.0.1
    • Similar Issues:

      Description

      After upgrading the TAP plugin from version 1.24 to version 2.0.1, the plugin fails to parse some TAP streams with the error:

      org.tap4j.parser.ParserException: Error parsing TAP Stream: Missing TAP Plan.
      at org.tap4j.parser.Tap13Parser.parseTapStream(Tap13Parser.java:230)
      at org.tap4j.parser.Tap13Parser.parseFile(Tap13Parser.java:193)
      at org.tap4j.plugin.TapParser.parse(TapParser.java:167)
      at org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:540)
      at org.tap4j.plugin.TapPublisher.performImpl(TapPublisher.java:412)
      at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:371)
      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:1766)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:410)
      Caused by: org.tap4j.parser.ParserException: Missing TAP Plan.
      at org.tap4j.parser.Tap13Parser.onFinish(Tap13Parser.java:393)
      at org.tap4j.parser.Tap13Parser.parseTapStream(Tap13Parser.java:227)
      ... 15 more

      I have since downgraded the plugin back to 1.24, and these same streams are now parsed correctly.

      The streams that were not parsed all contained special characters. An example of a stream that could not be parsed by the plugin is attached.

      I tested this stream in InstantTap, where it was parsed successfully.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            kinow Bruno P. Kinoshita
            Reporter:
            dspencer12 Daniel Spencer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: