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

MalformedByteSequenceException during analysis

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Not A Defect
    • Component/s: pmd-plugin
    • Labels:
      None
    • Environment:
      CentOS 5.5
      java version "1.6.0_17"
      OpenJDK Runtime Environment (IcedTea6 1.7.5) (rhel-1.16.b17.el5-i386)
      OpenJDK Server VM (build 14.0-b16, mixed mode)
      Jenkins ver. 1.399
    • Similar Issues:

      Description

      Build of job fails during PMD analysis with the following output:

      ...
      [CHECKSTYLE] Collecting checkstyle analysis files...
      [PMD] Collecting PMD analysis files...
      [PMD] Parsing of file /var/lib/jenkins/jobs/LSD/workspace/build/logs/pmd.xml failed due to an exception:

      com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
      at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
      at org.apache.commons.digester.Digester.parse(Digester.java:1666)
      at hudson.plugins.pmd.parser.PmdParser.parse(PmdParser.java:71)
      at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:52)
      at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:197)
      at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:176)
      at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:126)
      at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:29)
      at hudson.FilePath.act(FilePath.java:757)
      at hudson.FilePath.act(FilePath.java:739)
      at hudson.plugins.pmd.PmdPublisher.perform(PmdPublisher.java:134)
      at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:281)
      at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
      at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:644)
      at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:623)
      at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:601)
      at hudson.model.Build$RunnerImpl.post2(Build.java:159)
      at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:570)
      at hudson.model.Run.run(Run.java:1386)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:145)
      ...

      Further up in the log file, I see something that may have influence.

      [exec] ERROR: option "--error-severity=1" not known.

      [exec] Usage: phpcs [-nwlsavi] [--extensions=<extensions>] [--ignore=<patterns>]
      [exec] [--report=<report>] [--report-width=<reportWidth>] [--report-file=<reportfile>]
      [exec] [--config-set key value] [--config-delete key] [--config-show]
      [exec] [--standard=<standard>] [--sniffs=<sniffs>]
      [exec] [--generator=<generator>] [--tab-width=<tabWidth>] <file> ...
      [exec] -n Do not print warnings
      [exec] -w Print both warnings and errors (on by default)
      [exec] -l Local directory only, no recursion
      [exec] -s Show sniff codes in all reports
      [exec] -a Run interactively
      [exec] -v[v][v] Print verbose output
      [exec] -i Show a list of installed coding standards
      [exec] --help Print this help message
      [exec] --version Print version information
      [exec] <file> One or more files and/or directories to check
      [exec] <extensions> A comma separated list of file extensions to check
      [exec] (only valid if checking a directory)
      [exec] <patterns> A comma separated list of patterns that are used
      [exec] to ignore directories and files
      [exec] <sniffs> A comma separated list of sniff codes to limit the check to
      [exec] (all sniffs must be part of the specified standard)
      [exec] <standard> The name of the coding standard to use
      [exec] <tabWidth> The number of spaces each tab represents
      [exec] <generator> The name of a doc generator to use
      [exec] (forces doc generation instead of checking)
      [exec] <report> Print either the "full", "xml", "checkstyle",
      [exec] "csv", "emacs", "source", "summary" or "svnblame" report
      [exec] (the "full" report is printed by default)
      [exec] <reportWidth> How many columns wide screen reports should be printed
      [exec] <reportfile> Write the report to the specified file path
      [exec] (report is also written to screen)
      [exec] Result: 2

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          Seems that your xml file is broken. Can you please attach the file? Which version of PMD are you using?

          Show
          drulli Ulli Hafner added a comment - Seems that your xml file is broken. Can you please attach the file? Which version of PMD are you using?
          Hide
          patrickh patrick hanevold added a comment -

          I seems it was not a broken xml, but either missing or close to empty (due to no output, on failure or such).
          PMD Version 3.13.

          Sadly we managed to delete the build.

          Show
          patrickh patrick hanevold added a comment - I seems it was not a broken xml, but either missing or close to empty (due to no output, on failure or such). PMD Version 3.13. Sadly we managed to delete the build.
          Hide
          drulli Ulli Hafner added a comment -

          Ok, then I'm closing this issue.

          Show
          drulli Ulli Hafner added a comment - Ok, then I'm closing this issue.

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              patrickh patrick hanevold
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: